Skip to main content
Glama

Polymarket, Kalshi, Hyperliquid Funding Arbitrage & DEX Swap MCP

Scan Perpetual Futures Funding Rate Spreads

scan_perp_funding_spreads
Read-onlyIdempotent

Returns live annualized perpetual futures funding rate spreads across Hyperliquid L1, Kraken Futures, and Bybit Linear Perps.

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

Input Schema

NameRequiredDescriptionDefault
minSpreadAprPctNoMinimum annualized funding spread % (default 2.0)

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?

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds value beyond that by disclosing the venue scope and that data is live (not cached), but says nothing about failure modes of external exchanges, latency, throttling, or what a returned row contains.

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?

One front-loaded sentence with no filler; verb, output type, and venue scope all appear immediately. It is efficient, though a second sentence on result shape would have earned its place given there is no output schema.

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-optional-parameter read tool, the definition covers what it fetches but not what it returns — the structure of a 'spread' (per pair per venue comparison, fields included, ordering) is left unexplained and no output schema exists to compensate. The openWorldHint against three external exchanges also warrants a note on availability that is absent.

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% for the single optional parameter minSpreadAprPct, including its default of 2.0, so the schema carries the meaning. The description never mentions the spread filter or that it is expressed as annualized percent, adding no meaning beyond the structured field — the 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 (returns) plus a precise resource (annualized perpetual futures funding rate spreads) and names the three venues covered: Hyperliquid L1, Kraken Futures, and Bybit Linear Perps. An agent can tell this is a cross-venue funding-spread scanner rather than a Pendle, prediction-market, or bridge tool, though it never explicitly contrasts itself with siblings like compare_pendle_fixed_vs_funding.

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; the only hint is 'live', implying real-time arbitrage scanning. Nothing tells the agent how this differs from compare_pendle_fixed_vs_funding, which also touches funding, or when a static vs live snapshot is appropriate.

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.