Tools.

tenzro-mcp-server     mcp     https://mcp.tenzro.xyz/mcp
web-search-mcp        mcp     builtin://web-search-mcp
code-executor         mcp     builtin://code-executor
file-manager          native  builtin://file-manager
tenzro-a2a-server     api     https://a2a.tenzro.xyz

mcp tools speak MCP over Streamable HTTP. api tools wrap an HTTP API. Tools on the builtin:// scheme run inside the node that serves them, regardless of the type they declare.

Each built-in takes a tool name and a parameter object.

# web-search-mcp
web_search   { "query": "...", "limit": 10 }
url_fetch    { "url": "https://...", "max_bytes": 262144 }

# code-executor — runs a WASI 0.2 component, identified by the
# SHA-256 of the bytes you submit, under a fuel and deadline budget.
# "function" is an export inside tenzro:skill/skill@1.0.0
# and defaults to "invoke".
execute_component {
  "component_b64": "...",
  "function": "invoke",
  "input": { }
}

# file-manager — rooted at <data_dir>/agent_workspace,
# relative paths only
read    { "path": "notes/plan.md" }
write   { "path": "notes/plan.md", "content": "..." }
list    { "path": "notes" }
delete  { "path": "notes/plan.md" }

web-search-mcp needs the operator's builtins.search_url; code-executor needs the component sandbox, which a stock build includes. A node missing either does not register the tool, so discovery lists only what it can serve.

tenzro tool list
tenzro tool list --tool-type mcp
tenzro tool search retrieval
tenzro tool get <tool_id>
tenzro tool use <tool_id> --tool-name web_search --params '{"query":"..."}'
tenzro tool register --name web-search --description "Web search over MCP" \
  --endpoint https://tools.example.org/mcp --capabilities web-search