Tools Registry

The Tenzro tools registry is a decentralized catalog of MCP servers, API endpoints, and native capabilities that agents can discover and invoke. Tools are the actual external interfaces agents connect to for taking real-world actions. Unlike skills (which encode reasoning and logic), tools ARE the capabilities being invoked.

Tool Types

Built-in Tools

Seven tools are auto-registered in CF_TOOLS at node startup:

Registering a Tool

# Via CLI
tenzro tool register \
  --name "my-search-mcp" \
  --type mcp \
  --endpoint "https://my-server.example.com/mcp" \
  --description "Web search tool for agents" \
  --category search

# Via JSON-RPC
curl -X POST https://rpc.tenzro.network \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "method": "tenzro_registerTool",
    "params": {
      "name": "my-search-mcp",
      "version": "1.0.0",
      "tool_type": "mcp",
      "endpoint": "https://my-server.example.com/mcp",
      "description": "Web search tool for agents",
      "capabilities": ["web-search", "read-url"],
      "category": "search"
    },
    "id": 1
  }'

Discovering Tools

# List all tools
tenzro tool list

# Search by keyword
tenzro tool search --query "ethereum"

# Get tool details
tenzro tool get --tool-id "abc123..."

ToolDefinition Structure

pub struct ToolDefinition {
    pub tool_id: String,        // UUID v4
    pub name: String,           // e.g., "web-search-mcp"
    pub version: String,        // Semantic version
    pub tool_type: String,      // "mcp", "api", or "native"
    pub endpoint: String,       // MCP/API endpoint URL
    pub description: String,    // What this tool does
    pub capabilities: Vec<String>, // e.g., ["web-search", "read-url"]
    pub category: String,       // e.g., "search", "code", "data"
    pub creator_did: Option<String>, // DID of registrant
    pub status: ToolStatus,     // Active, Inactive, or Deprecated
    pub created_at: u64,        // Unix timestamp
    pub invocation_count: u64,  // Usage counter
}

Tools vs Skills