Skip to main content
Glama
yg-base-mcp
by ufo1898

arb

Fetches live Base arbitrage spreads across Aerodrome, Uniswap V3, and Sushi, including gas costs and break-even volume for round-trip trades.

Instructions

Base 跨所往返价差快照(Aerodrome / Uniswap V3 / Sushi,含 gas 与盈亏平衡体量) — 0.002 USDC per call (x402, Base USDC, no signup)

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": "arb"
  }
}

Input Schema

NameRequiredDescriptionDefault
_paymentNobase64 PAYMENT-SIGNATURE from a previous 402 challenge

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/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 valuable behavior: each call costs 0.002 USDC, billed via x402 on Base USDC with no signup. What it omits is the mechanics an agent most needs: that the first call returns a 402 challenge and must be retried with a payment signature, and whether failed or unpaid calls are charged.

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 line that front-loads what the tool returns, then the venues, then the price. Nothing is wasted, though the mixture of data description and payment metadata in one sentence makes it slightly harder to parse than a clean two-sentence split.

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 one-parameter paid data endpoint with no output schema and no annotations, the description covers the data content and the cost model reasonably well. It falls short on the payment retry lifecycle and on any hint of response shape, which is the main thing an agent cannot otherwise infer.

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?

Parameter count is one and schema coverage is 100%, with the schema itself explaining the base64 PAYMENT-SIGNATURE obtained from a previous 402 challenge. The description adds only the pricing context that motivates that parameter, not any new semantics. Baseline 3 is appropriate when the schema does the documentation.

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?

Names a specific resource and scope: a cross-exchange round-trip spread snapshot on Base across Aerodrome, Uniswap V3 and Sushi, enriched with gas and break-even size. That is a concrete verb-plus-resource statement an agent can act on. It does not, however, distinguish itself from the sibling free_sample or explain why one would pick this over a free snapshot.

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?

Usage context is implied rather than stated: the mention of gas and break-even size signals this is for arbitrage evaluation, and 'no signup' plus the per-call price signals a paid data endpoint. There is no explicit when-to-use, when-not-to-use, or reference to the free_sample sibling that presumably covers a cheaper variant.

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