Skip to main content
Glama

AgentFeed

by io.github.seekdaseek
OverviewDiscussionsAdmin

Funding radar

get_funding_radar
Read-onlyIdempotent

Funding radar over every Hyperliquid perp: 337 on 13 Oct 2026, 178 on the main dex and 159 on the HIP-3 dexes (stocks, indices, commodities, FX). Per perp: the current funding at its 8h equivalent, its 30-day z-score against its own settled history, the dex and asset class, and a flag on any |z| of 2 or more, most extreme first. By default it returns the perps with $10M and up of open interest; min_oi_usd changes that and 0 returns them all. Precomputed every 5 minutes with as_of; a snapshot older than 15 minutes answers 503 and is never billed. Costs 0.02 USDC per call (x402, USDC on Solana, Base, Polygon, Arbitrum or Arc).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topNoperps returned, most extreme first, 1-100, default 20
min_oi_usdNominimum open interest in USD: default 10000000 ($10M); 0 returns every perp the radar tracks

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesthe get_funding_radar payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_funding_radar
toolYesthe tool that produced this payload

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / min_oi_usd / description
      Previous value: -"minimum combined open interest in USD across the venues: default 10000000 ($10M); the radar tracks pairs from 5000000 ($5M), and lower values return that floor"New value: +"minimum open interest in USD: default 10000000 ($10M); 0 returns every perp the radar tracks"
    • changedInput schema / properties / top / description
      Previous value: -"symbols returned, most extreme first, 1-100, default 20"New value: +"perps returned, most extreme first, 1-100, default 20"
  2. Changed1 schema field changed
    • changedInput schema / properties / min_oi_usd / description
      Previous value: -"minimum combined open interest in USD across the venues, default 10000000; the radar tracks 5000000 and up"New value: +"minimum combined open interest in USD across the venues: default 10000000 ($10M); the radar tracks pairs from 5000000 ($5M), and lower values return that floor"
  3. Added

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond the read-only/idempotent annotations: it discloses the 5-minute precompute cadence, the as_of field, the 503-on-stale-snapshot rule (and that stale calls are never billed), and the 0.02 USDC x402 cost with supported chains. These are operationally decisive facts an agent cannot get from annotations.

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?

Dense but front-loaded: scope first, then returned fields, then filtering, then operational caveats. Every clause carries a distinct fact, though the pricing and chain list at the tail is slightly tangential.

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?

With an output schema handling return shape, the description still covers the things only prose can: default filtering, cost, staleness failure mode, and freshness guarantee. Nothing needed to invoke or interpret it correctly 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 description coverage is 100%, so both params (top, min_oi_usd) are already documented with ranges and defaults. The description restates the default threshold and the 0-returns-all behavior but adds no syntax or format detail beyond the schema, so the baseline of 3 applies.

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 verb and resource (funding radar over every Hyperliquid perp) and quantifies scope (337 perps, 178 main dex, 159 HIP-3). It enumerates the exact returned fields, so an agent knows what this produces without opening the schema.

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?

Explains the default behavior ($10M+ OI) and how min_oi_usd=0 returns everything, which implicitly guides usage, but never names or contrasts with close siblings like get_funding_extremes, get_funding_pulse, get_funding_history, or get_funding_rate. The agent must infer when this radar beats those alternatives.

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

All AgentFeed toolsInspect
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