Skip to main content
Glama

x402-perp-funding-radar

x402-perp-funding-radar: Cross-venue funding radar: the same perpetual's funding on Hyperliquid, dYdX, Bybit and Binance, normalised to one hourly basis and annualised, with mark price and open interest side by side, plus the cheapest venue to be long and the richest to be short.

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": "x402-perp-funding-radar"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetNo
limitNo
historyDaysNo
alertAnnualPctNo
minAnnualSpreadPctNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / alertAnnualPct
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / historyDays
      Added value: +{
      +  "type": "string"
      +}
  2. Changed3 schema fields changed
    • addedInput schema / properties / asset
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / limit
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / minAnnualSpreadPct
      Added value: +{
      +  "type": "string"
      +}
  3. Added

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the analytical transformations (normalized to one hourly basis, annualized) and that results are presented side by side across venues, which is genuine behavioral context. But it says nothing about whether funding is a live snapshot or a lookback, how missing venues are handled when a perp isn't listed on all four, payment/rate-limit characteristics implied by the x402 prefix, or freshness of mark price and open interest.

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?

It is a single dense sentence, front-loaded with the tool name and core concept, and no sentence is filler. The colon-and-comma chaining of clauses makes it slightly hard to parse, but it stays tight for the amount of scope it conveys.

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

Completeness2/5

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

With five parameters at 0% schema coverage, no annotations, and no output schema, the description is the only documentation an agent has. It describes the returned data adequately but omits any explanation of the threshold/spread-alert parameters, which look like the tool's key filtering behavior, and never clarifies units or accepted formats for the string-typed numeric inputs. That is a substantial gap for a tool of this complexity.

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 0% and all five parameters are typed as bare strings with no descriptions. The description explains the output concept but never touches the inputs: 'asset' is only obliquely implied by 'the same perpetual's funding', and 'limit', 'historyDays', 'alertAnnualPct', and 'minAnnualSpreadPct' are completely unexplained. Since the schema provides no guidance, the description should have compensated and does not.

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?

The description names a specific resource (cross-venue perpetual funding) and enumerates the four venues covered, the normalization (hourly basis, annualized), and the derived outputs (mark price, open interest, cheapest long / richest short venue). That is far more specific than the name alone. It does not, however, distinguish itself from clearly overlapping siblings such as x402-perp-funding-arb, x402-perp-funding-radar-deep, or x402-funding-rate, leaving the agent to guess which variant to call.

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: the mention of 'cheapest venue to be long and the richest to be short' signals a funding-arbitrage comparison use case, but there is no explicit when-to-use, when-not-to-use, or alternative-naming guidance. An agent facing x402-perp-funding-arb and x402-perp-funding-radar-deep alongside this tool must infer the boundary from the description's scope alone.

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