bsc-dex-spread

BSC cross-DEX price & spread

get_dex_spread

Compare real-time prices across PancakeSwap v2 and v3 on BSC to identify the best buy and sell venues and calculate cross-DEX spread in bps.

Instructions

Real-time cross-DEX price & spread for PancakeSwap v2+v3 on BSC. Params: pair=SYM/SYM (e.g. WBNB/USDC), optional fee=v3 tier. Returns per-venue prices, best buy/sell, gross cross-DEX spread (bps), liquidity, and block number. Costs $0.01 USDC per call on Base mainnet (eip155:8453), paid automatically from the wallet in EVM_PRIVATE_KEY.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pair": "<pair>"
    },
    "name": "get_dex_spread"
  }
}

Input Schema

Name	Required	Description	Default
`fee`	No	Optional PancakeSwap v3 fee tier to restrict the v3 probe (e.g. 100, 500, 2500, 10000). Omit to probe all v3 tiers + v2.
`pair`	Yes	Token pair as SYM/SYM; first symbol is the USD-priceable side (e.g. WBNB/USDC, WBNB/USDT, CAKE/WBNB).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 29, 2026

TDQS

A4.4/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. It discloses return fields (per-venue prices, best buy/sell, spread in bps, liquidity, block number), real-time nature, and cost ($0.01 USDC). Could mention rate limits or potential failures, but already quite transparent.

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?

Two sentences plus a parameter line, tightly packed with essential information. No fluff, every sentence adds value. Front-loaded with purpose and immediate context.

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 explains return values adequately. Covers purpose, parameters, return fields, and cost. Missing details like caching behavior or network requirements, but overall complete for the tool's low complexity.

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

Parameters4/5

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

Schema coverage is 100% (both parameters documented). Description adds value: clarifies pair symbol ordering ('first symbol is the USD-priceable side') and fee behavior ('Omit to probe all v3 tiers + v2'). This goes beyond bare schema meaning.

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 'Real-time cross-DEX price & spread for PancakeSwap v2+v3 on BSC.' The verb 'get' and resource 'dex_spread' are specific, and the description adds detail about the exact feature set. No siblings exist, so differentiation is not required.

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?

Includes parameter format examples and notes on optional fee tier, but lacks explicit guidance on when to use versus alternatives or when not to use. However, with no sibling tools, the description is contextually sufficient, earning a 4.

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

Deploy Server

Other Tools

get_dex_spreadA