Skip to main content
Glama

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

defi_arbitrage_radar

[$0.25] Measure cross-venue DEX spot price dispersion in basis points alongside $5M+ TVL DeFi yield-carry opportunities using keyless DexScreener and DeFiLlama data.

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_arbitrage_radar"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetNoAsset ticker (e.g. 'WETH', 'USDC', 'cbBTC', 'SOL')WETH
chainNoTarget chain ('base', 'ethereum', 'arbitrum', or 'all')base
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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does add real behavioural context: keyless DexScreener/DeFiLlama sourcing, a $5M+ TVL floor, basis-point units, and a $0.25 cost — but it says nothing about rate limits, caching, freshness of the data, or what the response actually looks like (and no output schema exists to fill that gap).

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 dense sentence with no filler, though the cost marker precedes the verb and two distinct capabilities are packed with 'alongside' rather than structured, which slightly buries the primary action.

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?

With three all-optional, fully documented parameters and no output schema, the description should explain what comes back. It names the metrics and units of the dispersion side and the TVL filter, but leaves the yield-carry payload unspecified and does not mention degradation or caching behaviour beyond what the parameter schema already states.

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 the schema already explains asset, chain, and the timeout_ms/degraded behaviour in more detail than the description does. The description adds only indirect meaning ('cross-venue' implying chain scoping, the TVL filter not being a parameter). Baseline 3 applies.

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?

States a specific verb ('Measure') and two concrete resources: cross-venue DEX spot price dispersion in basis points and $5M+ TVL yield-carry opportunities. That is far more specific than a tautology and lets an agent distinguish it from generic price or yield lookups, though it never names the neighbouring yield/convergence tools it overlaps with.

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

Usage Guidelines3/5

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

Use case is only implied: the tool reads as 'use this to find arbitrage dispersion and carry trades'. There is no explicit when-to-use or when-not-to-use statement, no prerequisites, and no routing to alternatives; the bracketed price tag is cost signalling, not guidance.

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