Crypto, web, finance and app data tools

Perp Funding & OI Across Exchanges

funding_compare

A coin's perpetual funding rate and open interest on OKX, Bitget, Gate, Kraken Futures and Hyperliquid, annualized side by side, with the widest long/short funding spread. Use for funding arbitrage, crowding and sentiment checks.

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

Input Schema

Name	Required	Description	Default
`coin`	No		BTC

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 24, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses data sources and computed outputs (annualized side-by-side, widest spread), but omits data freshness, rate limits, permissions, and whether values are live or delayed. The output schema reduces the need to explain return values.

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 tight sentences, front-loaded with what data is returned and from which exchanges, followed by use cases. No filler or repetition.

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?

For a single-parameter read tool with an output schema, it covers exchanges, metrics, computations, and usage contexts well. Remaining gaps are coin input format and operational details such as freshness or rate limits.

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?

There is one parameter, coin, with 0% schema description coverage. The description says 'A coin's' but provides no accepted symbol format, case handling, or valid values, so it does not compensate for the missing schema documentation.

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?

Names specific metrics (perpetual funding rate and open interest), five exchanges, annualization, side-by-side comparison, and widest long/short funding spread. This clearly distinguishes it from a generic sibling like perp_funding_rates.

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?

Explicitly states use cases: funding arbitrage, crowding, and sentiment checks. However, it does not say when to choose this over sibling perp_funding_rates or mention any exclusions.

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

All Crypto, web, finance and app data tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?