Skip to main content
Glama

PerpMetric perpetuals data

Funding spreads across venues

find_funding_spreads
Read-onlyIdempotent

Every asset listed on two or more venues, ranked by the gap in annualized funding (APR %) between its highest- and lowest-paying venue, with open interest and volume per leg. One call instead of compare_venues per asset. Gross differential only, not a trade signal.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
min_oi_usdNoMinimum open interest per venue leg.
min_venuesNo
min_volume_24h_usdNoMinimum 24h volume per venue leg.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-obvious context beyond that: the ranking is a gross differential and explicitly not a trade signal, which prevents a costly misinterpretation of the output. It omits result ordering/pagination behavior, keeping it below 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, both front-loaded with the highest-value information: what is returned and how it is ranked, then the sibling substitution and the interpretation caveat. No filler or restatement of the title.

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?

With no output schema, the description carries the burden of describing returns and does so adequately (ranked list, gap metric, per-leg OI and volume). The main residual gap is that it never explains the effect of limit or min_venues on the result set, which matters for a ranked-list tool.

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

Parameters2/5

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

Schema description coverage is only 50%: min_oi_usd and min_volume_24h_usd are documented in the schema, while limit and min_venues are not. The description mentions no parameters at all, so it does nothing to compensate for the undocumented half or to clarify that the filters apply per venue leg rather than in aggregate.

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?

The description names a specific resource (assets listed on 2+ venues) and a specific ranking metric (gap in annualized funding APR between highest- and lowest-paying venue), plus the per-leg payload (open interest, volume). It explicitly distinguishes itself from compare_venues, so an agent can tell the two apart without opening either schema.

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?

"One call instead of compare_venues per asset" gives a clear selection rule against a named sibling, which is exactly the kind of routing guidance that matters here. It stops short of stating exclusions (e.g. what happens for single-venue assets, or when a per-asset comparison is still preferable), so it is strong but not exhaustive.

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