Skip to main content
Glama

x402-services

by ai.firmbrain

exec_quote

Best-route swap quote across DEXes (KyberSwap aggregator): expected output, USD in/out, price impact %, gas cost, and the DEXes routed through. Send { chain, tokenIn, tokenOut, amountIn } (amountIn in smallest units). Quote only — never executes. Pre-trade routing for trading agents. [x402 paid tool — price $0.05; POST /api/exec/quote]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainNobase (default), ethereum, arbitrum, polygon, optimism, bsc, avax
tokenInYes0x token address to sell
amountInYesAmount to sell in smallest units (wei)
tokenOutYes0x token address to buy

TDQS

A4.2/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. Discloses it's non-executing, uses KyberSwap, lists return fields. No contradictions.

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

Conciseness5/5

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

Three sentences covering purpose, usage, and key constraint. No fluff. Pricing/endpoint info appended neatly.

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 no output schema, description adequately explains return fields. Covers required parameters and chain options. Could explicitly list all return fields, but current is sufficient.

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

Parameters3/5

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

Schema covers all 4 parameters with descriptions. The description reinforces amountIn in smallest units, but does not add substantial new meaning beyond schema.

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?

Clearly states it provides best-route swap quotes across DEXes via KyberSwap aggregator, listing return fields. It distinguishes from execution tools by explicitly saying 'Quote only — never executes.'

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?

Tells what to send (chain, tokenIn, tokenOut, amountIn) and that it's for pre-trade routing. Implicitly when not to execute, but no explicit alternatives.

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

All x402-services toolsInspect
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
Disambiguation4/5

Tools are organized by domain prefix (e.g., 'crypto_', 'rh_', 'snipe_'), which helps distinguish between areas. Within each domain, they serve distinct purposes, though some overlap between domains exists (e.g., price data appears in multiple groups). Overall, an agent can navigate effectively.

Naming Consistency5/5

All tool names follow a consistent snake_case pattern with a domain prefix and a verb_noun combination (e.g., 'compliance_risk', 'rh_stock', 'snipe_honeypot'). This makes the API predictable and easy to explore.

Tool Count2/5

With 159 tools, the server is extremely large. While the broad scope of web3 and utility functions justifies many tools, the count is significantly above the typical range for a coherent toolkit, potentially overwhelming agents and increasing selection error.

Completeness4/5

The toolkit covers a wide range of web3 operations: crypto, DeFi, compliance, safety, scheduling, memory, etc. There are no obvious major gaps for its intended purpose, though some niche areas might be missing.

Resources