Get the live Routheus product catalog: DEX endpoints, the FREE tier (single-input swap quotes and quote+calldata are free, rate-limited per IP — no payment or key), per-call USDC prices for paid products, supported EVM chains, x402 payment details, and a contact email for custom/higher-limit plans. Call this first to learn what's available, what's free, and what costs.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. Details tool's read-only nature (getting catalog), free tier with rate limits, and response composition. Does not mention authentication or side effects, but those are implicit for a read-only catalog tool.
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 but efficiently lists key contents and purpose. Front-loaded with the main action. Could be slightly more concise, but 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?
Description is fully self-contained for a discovery tool with no parameters and no output schema. It explains what the tool returns, why to use it, and how it relates to free vs. paid products. No gaps.
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?
No parameters, so schema coverage is 100%. Description adds value by explaining what the returned catalog contains beyond the empty schema, effectively compensating for the lack of parameters.
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?
Clearly states it retrieves the live Routheus product catalog with specific contents (DEX endpoints, free tier, paid products, etc.). Distinguishes from siblings like routheus_chains and routheus_price_offer by being the first-stop discovery tool.
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?
Explicitly instructs 'Call this first to learn what's available, what's free, and what costs,' providing clear usage context. Lacks explicit when-not-to-use or alternative references, but the directive is strong and appropriate.
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 serves a distinct purpose: catalog provides overall info, chains lists supported chains, price_offer gets pricing details. No overlap or ambiguity.
All tools follow the pattern 'routheus_<noun>', where the noun describes the resource: catalog, chains, price_offer. Consistent and predictable.
Three tools is minimal but sufficient for the server's purpose of providing product info and pricing. Could include an execution tool, but the delegation to x402 client keeps it concise.
Covers the essential operations: catalog, chain listing, and pricing/offer retrieval. The missing swap execution is intentionally delegated to an external client, so no critical gap.
