Robinhood Chain read-only eth_call: query any contract view function. Send { to, data, from? }. [x402 paid tool — price $0.005; POST /api/rhchain/call]
| Name | Required | Description | Default |
|---|---|---|---|
| to | Yes | 0x contract | |
| data | Yes | 0x calldata | |
| from | No | Optional caller |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses read-only behavior and pricing ($0.005) beyond the schema, but without annotations, lacks info on error handling, limitations, or auth requirements.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Extremely concise with front-loaded key info: purpose, parameters, and cost. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Adequate for a simple tool with clear schema, but lacks description of return format or examples, which would help given no output schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and parameter descriptions are clear. The description merely restates parameters, adding no extra semantic value.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'read-only eth_call: query any contract view function', indicating a specific verb and resource. It distinguishes from sibling tools like rhchain_tx (write) and specific data tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implies usage for querying any view function, but does not explicitly state when not to use or provide alternatives among the many sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.