Skip to main content
Glama

x402 Data API (Crypto, DeFi, SEC EDGAR, Search, Embeddings, Whisper, OCR)

defi_intent_routing

[$0.15] Score cross-chain intent settlement routes across Base, Arbitrum, Optimism, and Ethereum by combining DEX liquidity depth, slippage, and live RPC gas costs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "defi_intent_routing"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetNoAsset symbol (e.g. 'USDC', 'WETH', 'cbBTC')USDC
amount_usdNoIntent transfer/swap size in USD (default $25,000)
timeout_msNoOptional deadline in ms. If the local LLM would exceed it, the response comes back fast with "degraded": true and non-LLM/cached data
source_chainNoOrigin chain (e.g. 'base', 'arbitrum', 'optimism', 'ethereum')base
destination_chainNoDestination chainarbitrum

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden, and it does disclose useful behavioral context: per-call price ($0.15), the data sources blended into the score (DEX liquidity depth, slippage, live RPC gas costs), and chain coverage. It does not say whether the tool only scores or actually submits/settles an intent, nor does it mention read-only nature, rate limits, or the degraded-response behavior that the schema references.

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

Conciseness4/5

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

A single front-loaded sentence with the verb first and the price tag bracketed up front; nothing is padded or restated. It is arguably too terse for a tool with no annotations and no output schema, but that is a completeness issue rather than a verbosity one.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter scoring tool with no annotations and no output schema, the description omits what a 'score' result actually looks like (per-route breakdown? ranked list? single best route?) and whether any side effect occurs. It is enough to know roughly what the call does, but not enough to confidently interpret the result.

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 description coverage is 100%, so every parameter (asset, amount_usd, timeout_ms, source_chain, destination_chain) is already documented with defaults and bounds. The description adds only that routes are scored across the four named chains, which slightly clarifies valid chain values but goes no further.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb ('Score') and a specific resource ('cross-chain intent settlement routes'), and enumerates the supported chains (Base, Arbitrum, Optimism, Ethereum). It is clearly distinct from sibling tools like defi_arbitrage_radar or defi_yield_matrix, but it never explicitly contrasts itself with them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, no prerequisites (e.g. wallet, auth, chain support constraints), and no named alternatives. The agent must infer from the one-line purpose statement that this is the route-scoring tool rather than an execution or arbitrage tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources