Skip to main content
Glama

Perp funding

perp_funding
Read-onlyIdempotent

Live perpetual futures funding rates, 1h/8h/APR yield, mark-oracle basis, open interest, and cross-venue arbitrage spreads across Hyperliquid, Binance USD-M, and Bybit Linear. $0.005 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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

Input Schema

NameRequiredDescriptionDefault
sortNospread (default), apr, oi, or volume
limitNo1-50 (default 20)
venueNoall (default), hyperliquid, binance, or bybit
symbolNooptional comma-separated ticker(s) like BTC,ETH,SOL,HYPE
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.
minOiUsdNominimum open interest USD

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations (which only state readOnly/idempotent/openWorld/non-destructive), the description discloses the concrete cost ($0.005 per call), accepted payment assets and chains, and the wallet-signing requirement — real behavioral context an agent needs before calling. It does not mention rate limits, caching/freshness of 'live' data, or what happens if payment is malformed, which keeps it from a 5.

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?

Three sentences, front-loaded with what the agent gets, then price, then the exact invocation protocol. Every clause carries information; nothing is restated from the title or schema.

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 six optional parameters, all fully described, no output schema, and an unusual paid-call mechanism, the description covers the metrics returned, the venues, the cost, and the two-step payment flow adequately. It leaves the response shape (field names/structure) unspecified, which matters somewhat given there is no output schema.

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 already 100%, so the baseline is 3, but the description adds meaning for the hardest parameter by explaining how a `payment` payload is obtained (call first without it, sign the returned terms) rather than just what it is. The sort/limit/venue/symbol/minOiUsd parameters gain nothing beyond the schema, so the lift is partial.

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 opening sentence names a specific verb-adjacent resource set — 'Live perpetual futures funding rates, 1h/8h/APR yield, mark-oracle basis, open interest, and cross-venue arbitrage spreads' — and scopes the venues (Hyperliquid, Binance USD-M, Bybit Linear). An agent knows exactly what data comes back. It stops short of naming when a sibling such as funding_gap is the better choice, so it is clear but not sibling-differentiated.

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?

The x402 two-step protocol is spelled out explicitly ('Call once without `payment` for the terms, sign them with your own wallet, call again with `payment`'), which is genuine when/how-to-invoke guidance an agent would otherwise have to guess. However, it gives no selection guidance against alternatives in the catalog and no exclusions for when this tool is inappropriate.

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