One-call market snapshot of Epsilon (Robinhood Chain DEX): top tokens by 30-day volume, 24h volume aggregates, and engine-wide order/fill stats. Good first call for market context.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds that this is a one-call snapshot and enumerates the returned data categories, but it does not disclose output format, pagination, or other behavioral nuances. With annotations present, this is acceptable but not rich.
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?
The description is two sentences with no filler. The key concept 'one-call market snapshot' is front-loaded, and the content breakdown follows immediately. Every phrase 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?
For a zero-parameter, read-only tool with no output schema, this description is complete enough. It tells the agent exactly what data to expect and positions it as a first-call market context tool. No missing information prevents correct invocation.
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?
The tool has zero parameters, and the input schema is empty, so the baseline is 4. The description adds context by explaining what the no-parameter call returns, which helps the agent understand why no arguments are needed. No schema compensation is required.
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 the tool returns a market snapshot for Epsilon DEX with specific content: top tokens by 30-day volume, 24h volume aggregates, and engine-wide order/fill stats. This is specific enough to understand the resource and scope, though it does not explicitly contrast with siblings like market_stats or token_volume.
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?
'Good first call for market context' gives a clear usage context and implies this is the starting point for market-level queries. It stops short of explicitly saying when not to use it or naming alternatives, so it lacks full routing guidance.
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.
Most tools are clearly separated by resource (orders, quotes, routes, tokens, docs, examples), but market_stats, get_market_overview, and token_volume overlap on volume/engine-wide stats, and get_quote/get_route are closely related. Descriptions mitigate most misselection.
Most accessors use get_/list_/search_ verbs, but five tools (error_catalog, market_stats, order_preflight, recent_swaps, token_volume) use bare noun phrases instead of a consistent verb-first pattern. All names are snake_case and readable, so the mixed verbs are a moderate inconsistency.
At 15 tools the server is at the top of the ideal range and each area (market data, orders, quotes/routing, docs, examples) is represented. A few overlapping stats/volume tools make it feel slightly heavier than necessary, but the count is not a problem.
The read-only surface is fairly complete: quotes, routes, orderbook, order status/list, market stats, token search, docs, examples, and error catalog. However, there are no tools to create/submit or cancel orders, and no wallet/balance/allowance tools, so agents cannot complete an actual trade from quote to execution. This is a notable gap if the server is meant to support trading, not just research/development.