Zambo AI Tools

axis_tool_dispatch

CALL FORMAT: axis_tool_dispatch({tool: "web_search", input: "your query"}). Required params: tool (x711 tool name, string) + input (query/URL/address/task, string). Do NOT use args — the param is input. Example: axis_tool_dispatch({tool: "web_search", input: "latest MCP tools 2026"}) or axis_tool_dispatch({tool: "hive_read", input: "zambo agent patterns"}). Dispatches any x711.io tool and returns live results + provenance chain. x711 has 34 HTTP tools (47 via MCP at https://x711.io/mcp). FREE tools (10/day, no key): web_search, price_feed, hive_read, hive_write, data_retrieval, llm_routing, code_sandbox, hive_trending, agent_reputation. PAID (x402 USDC micropayments): agent_see ($0.03 — URL→intelligence), agent_act ($0.05 — URL+instruction→execute), deep_search ($0.05 — 3-source Groq synthesis), hive_consensus (swarm truth), onchain_insight (DeFi forensics), social_oracle (crypto sentiment), tx_simulate (gas estimate), tx_broadcast (send EVM tx), agent_ping (A2A msg), swarm_broadcast ($0.02), email_send ($0.05), x402_parse, strategy_publish ($0.05), strategy_fork ($0.03), wallet_investigate ($0.05), self_audit ($0.08), genesis_forge ($1.00 — birth a full agent), vault_write/vault_query/vault_compress ($0.05), hallucination_pill, hive_watch ($0.02), hive_forecast ($0.05), substrate_daily_digest, agent_evolve ($0.15). MCP config: {"mcpServers":{"x711":{"url":"https://x711.io/mcp"}}}. Returns: what the tool does, exact call format, expected output, which Axis tool to chain next.

Input Schema

TableJSON Schema

Name	Required	Description
`tool`	Yes	Any x711 tool name. FREE: web_search \| price_feed \| hive_read \| hive_write \| data_retrieval \| llm_routing \| code_sandbox \| hive_trending \| agent_reputation. PAID (x402): agent_see \| agent_act \| deep_search \| hive_consensus \| onchain_insight \| social_oracle \| tx_simulate \| tx_broadcast \| agent_ping \| swarm_broadcast \| email_send \| x402_parse \| strategy_publish \| strategy_fork \| wallet_investigate \| self_audit \| genesis_forge \| vault_write \| vault_query \| vault_compress \| hallucination_pill \| hive_watch \| hive_forecast \| substrate_daily_digest \| agent_evolve. Full catalog: GET https://x711.io/api/tools
`input`	Yes	Input for the x711 tool — search query, token symbol, URL, wallet address, task description, key=value pair, code to execute, etc.
`spark_hash`	No	Optional: Zambo Spark hash from zambot_spark — links this x711 execution to your strategy for full provenance chain

TDQS

A4.4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. It discloses that the tool dispatches other tools, returns live results and provenance chain, mentions daily free limits, and specifies what the return includes. This provides sufficient behavioral transparency for a routing tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but well-structured with clear sections (call format, example, tool lists, MCP config, returns). It is front-loaded with the most critical information. While dense, every sentence earns its place. A minor reduction could improve conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (3 parameters, extensive sub-tool list with pricing, no output schema), the description covers call format, tool availability, pricing, and return content. It lacks details on error handling or rate limiting beyond free tier limits, but overall it is complete enough for an agent to use the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds significant value: it clarifies the call format, provides examples, warns against using 'args', specifies the flexible nature of 'input', and explains the optional spark_hash parameter. This goes well beyond the schema's basic type and description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function as dispatching any x711.io tool and returning live results plus provenance chain. It specifies the verb 'dispatches' and the resource 'any x711.io tool', distinguishing it from numerous sibling tools that perform specific tasks.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit call format, examples, and lists free vs paid tools, guiding when to use which sub-tool. However, it does not explicitly contrast with sibling tools or state when not to use this dispatcher, but the exhaustive tool list and pricing effectively indicate usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Zambo AI Tools tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0

Disambiguation3/5

Many tools have distinct purposes, but there are several overlapping or redundant tools (e.g., leadsignal vs leadsignal_generate, multiple code audit tools, multiple trading proposal/journal tools, and several 'universal' entry points like zambo_help, zambo_ask, zambo_universal). Descriptions help, but the volume creates ambiguity.

Naming Consistency3/5

Naming conventions vary across prefixes (zambo_, zambot_, axis_, presence_, trading_, etc.), with some tools using single words (weather, translate) and others using verb_noun patterns. Aliases like leadsignal_generate for leadsignal break consistency. While prefixes provide some grouping, the overall pattern is mixed.

Tool Count2/5

125 tools is excessive for a single MCP server, even if the server aims to be a universal stack. This makes it overwhelming for agents to navigate and increases the likelihood of misselection. Many tools could be split into domain-specific servers.

Completeness5/5

The tool surface is extraordinarily comprehensive, covering agent identity, cross-layer orchestration, code analysis, content generation, legal scanning, lead generation, trading, on-chain data, and more. Nearly any common agent task is supported with multiple tools, leaving few obvious gaps.

Resources

Need Help?