Skip to main content
Glama
verifystack-x402-mcp

verifystack-x402-mcp

Official

verifystack_live_funding_arb

Scan live perpetual funding-rate arbitrage across Hyperliquid, dYdX v4, and Gate.io, normalized to hourly spreads and gross APR, then filter results by asset and minimum APR.

Instructions

Paid x402 API ($0.01 USDC on Base): Real-time cross-exchange perpetual funding rate arbitrage scanner aggregating Hyperliquid, dYdX v4, and Gate.io normalized to hourly spreads and gross APR.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (1-100, default 15)
minAprNoMinimum gross annualized APR percent filter
symbolNoOptional asset ticker filter (e.g. BTC, ETH, SOL)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does meaningful work: it discloses that the tool is a paid x402 endpoint with a specific price and settlement chain, and that results are real-time and normalized to hourly spreads and gross APR. It omits rate limits, payment-failure behavior, and result ordering, which keeps it short of a 5.

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, front-loaded with the payment requirement before the capability, with no filler. It is information-packed but readable; a slight split into cost and capability clauses would help scanning.

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?

All three parameters are optional and fully described in the schema, and the description covers sourcing and normalization. With no output schema, however, it should say more about the returned record shape (per-venue rows? per-symbol ranking?) and whether results are sorted, which an agent needs to consume the output.

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 all three parameters (limit, minApr, symbol) are already documented in structured form. The description only marginally enriches this by tying 'gross APR' to the minApr filter and implying symbol filtering, so baseline 3 is appropriate.

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 concrete resource and action: a cross-exchange perpetual funding-rate arbitrage scanner, naming the three venues (Hyperliquid, dYdX v4, Gate.io) and the output normalization (hourly spreads, gross APR). It never explicitly contrasts with siblings like verifystack_arb_net_profit, so differentiation is left to inference.

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 is only implied by the resource name — an agent can infer this is for scanning funding-rate dislocations across venues. The description adds a useful cost/precondition note ($0.01 USDC on Base via x402) but gives no when-not-to-use conditions and no pointer to the net-profit sibling for fee-adjusted analysis.

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