Proxy a free read-only Ethereum JSON-RPC query through DDG's private Reth node (sync-gated).
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | ||
| agent_id | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so description carries full burden. It discloses read-only nature and sync-gating (node sync requirement), but lacks details on error conditions, rate limits, or authentication needs. Vague term 'sync-gated' could be clearer.
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?
Single sentence with no unnecessary words. Front-loaded with key information (proxy, free, read-only, Reth node, sync-gated). Every part earns its place.
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?
Output schema exists (not shown), which may document return values. But description lacks request formatting details, allowed methods, or examples. For a query proxy tool, more context would enhance usability, though not critically missing.
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 description coverage is 0%, so description must add meaning. It only says 'proxy a query' without explaining the 'body' parameter structure (e.g., JSON-RPC format) or 'agent_id' purpose. Very little added value beyond parameter names and types.
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?
Description clearly states the tool proxies a free read-only Ethereum JSON-RPC query through a DDG private Reth node. Verb and resource are specific, and it distinguishes from sibling tools like ddg_data_query or ddg_tx_smoke_test which serve different purposes.
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?
No explicit guidance on when to use this tool vs alternatives. The 'free read-only' hint suggests it's for Ethereum data queries, but no when-not or alternative tool mentions. Usage context is implied by the tool name and description but not explicitly clarified.
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.
Each tool has a clearly distinct purpose, ranging from status checks to order management to payment processing. Despite the large number, descriptions make them easy to differentiate, with no obvious overlap.
All tools share the 'ddg_' prefix, but naming patterns vary: some use verb_noun (e.g., ddg_list_models) while others use noun_noun (e.g., ddg_agent_status). This mix reduces consistency, though readability remains acceptable.
With 25 tools, the count is at the high end but scales to cover diverse aspects of payable services (status, orders, payments, models, x402). Minor consolidation could be possible, but most tools earn their place.
The tool surface covers core workflows like order lifecycle, payment, and service discovery. Minor gaps (e.g., no cancellation or refund tools) exist but do not severely hinder typical agent interactions.
