Skip to main content
Glama

Perps funding rates (x402)

perps_funding

Read-onlyIdempotent

$0.002 via x402: Funding rates for all perps: current Hyperliquid funding, predicted funding on Hyperliquid, Binance and Bybit with next funding time, sorted by current funding; top and bottom extremes; filter coins=BTC,ETH or limit. Pay 0.002 USDC through https://store.agentexchange.work/gw/perps/funding?limit=20 Via the Agent Exchange store gateway; settled by Coinbase.

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

Input Schema

NameRequiredDescriptionDefault
coinsNocomma list to filter
limitNo1..300, default 50
x_paymentNoSigned x402 payment payload (optional; without it the answer is the price)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so safety is covered; the description adds genuinely non-obvious behavior: the tool is paid ($0.002 USDC over x402, settled by Coinbase via the Agent Exchange gateway) and omitting the payment payload returns the price instead of data. That payment behavior is impossible to derive from annotations or schema. It loses a point for not stating response shape or rate/size limits beyond the 300 cap already in the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The price is front-loaded, which is useful, but the body is a single colon-chained run-on that mixes data coverage, filtering, sorting, a raw gateway URL and payment settlement into one breath. The price is also stated twice ('$0.002' and '0.002 USDC') and the URL is buried mid-sentence rather than placed where an agent expects payment instructions.

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, three optional parameters, and a simple flat object, the description carries almost everything needed: which venues, what is predicted vs. current, sort order, filter/limit options, and the full payment precondition including the no-payment fallback. Only the returned record shape and any pagination beyond the 300 limit are unaddressed.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline would be 3, but the description adds value by showing a concrete coins example ('BTC,ETH') and by explaining the x_payment flow ('Pay 0.002 USDC through <url>' and that without payment 'the answer is the price'). Those are semantic additions beyond the terse schema strings, though limit bounds (1..300, default 50) are left to the schema.

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 the resource precisely: funding rates for all perps, with the exact data sources (current and predicted Hyperliquid funding, Binance, Bybit), next funding time, and sort order. That is far more specific than a restated title. It stops short of a 5 because it never contrasts itself with perps_market or perps_mids, relying on the reader to infer that those siblings cover prices rather than funding.

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 implied through the optional filters ('filter coins=BTC,ETH or limit') and the aggregation features ('top and bottom extremes'), so an agent can guess how to tailor a call. There is no explicit when-to-use versus alternative, no statement about when this is preferable to perps_market/perps_mids, and no guidance on when the limit vs. coins filter combination matters.

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