SiteCheck Agent Intel & Dev

Current perpetual-futures funding rate for one coin

agent_intel_perp_funding_rate_heatmap

Read-only

Current perpetual-futures funding rate for one coin (USDT-margined) on Binance, OKX and Bybit, with each rate annualised (3 payments a day), mark price, and from Bybit: open interest value and the long/short account ratio. A table of exchanges, not a time-series heatmap; funding history is not included. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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

Input Schema

Name	Required	Description	Default
`symbol`	No	Coin ticker, 2 to 10 letters, e.g. BTC, ETH, SOL (default BTC)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations only cover read-only and open-world; the description adds the economically critical behavior: $0.002 USDC per successful call via x402 on Base, Solana or Arc, and that failed calls are not charged. It also discloses per-exchange field coverage (Bybit-only fields), which tells the agent results are asymmetric across sources.

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, front-loaded with the core capability, followed by scope exclusions and cost. Every clause carries information an agent needs (annualisation convention, exchange coverage, heatmap disambiguation, payment model) with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists, yet the description still summarises returned fields and their per-exchange variance, which is the main ambiguity for a multi-source aggregator. Combined with the cost and payment details, nothing an agent needs to invoke or budget for the call is missing.

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 coverage is 100% and the single 'symbol' parameter already documents ticker format, length and the BTC default. The description adds nothing about symbol handling, so the baseline 3 applies — the schema does all the work here.

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?

States a specific resource and scope: current perp funding rate for one coin across Binance, OKX and Bybit, annualised, with mark price plus Bybit open interest and long/short ratio. It also pre-empts the misleading tool name by declaring 'A table of exchanges, not a time-series heatmap', so an agent can distinguish it from any history-oriented sibling.

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 the negative case ('funding history is not included') and clarifies the output shape, which steers an agent away from expecting a time series. It stops short of naming a concrete alternative tool for historical funding data, so the routing guidance is clear but not fully closed.

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

All SiteCheck Agent Intel & Dev tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?