Skip to main content
Glama

Perp Funding Rates: 5 venues in one call

Funding feed pass: 24 hours ($0.250) or 7 days ($1.000)

funding_feed_pass

Buy a pass for the funding feed: plan "24h" is one $0.250 payment, plan "7d" is one $1.000 payment for 7 days (x402 over MCP, USDC on Base), instead of $0.002 per call. Returns a bearer token (pass it as arguments.pass of funding_rates, or as "Authorization: Bearer " on MCP or HTTP requests to GET /v1/funding-rates) plus the current BTC/ETH/SOL funding snapshot. The 24h pass is worth it above about 125 calls a day (every ~12 minutes); the 7-day pass above about 72 calls a day, every day. Fair use: at most one call every 10 seconds; data may be cached up to 20 seconds. If no venue answers, nothing is 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": "funding_feed_pass"
  }
}

Input Schema

NameRequiredDescriptionDefault
planNoWhich pass to buy: "24h" (default) or "7d"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say the operation is not read-only and touches open world; the description adds the payment rail (x402, USDC on Base), what is returned (bearer token plus a BTC/ETH/SOL snapshot), fair-use rate limit of one call per 10 seconds, caching up to 20 seconds, and the no-charge guarantee when no venue responds. Nothing here contradicts readOnlyHint=false, and the repeated-payment risk is implicit in the non-idempotent annotation and per-plan pricing.

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?

Purpose is front-loaded, followed by plan pricing, token usage, and unit economics in a logical order with almost no filler. It is dense with parentheticals and runs long for a single optional parameter, but each sentence carries information an agent needs before paying.

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?

For a one-parameter purchase tool with no output schema, the description covers cost, duration, returned artifact, downstream usage, rate limits, caching, and failure billing. An agent has everything needed to decide and invoke correctly.

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% and the enum already lists "24h"/"7d", so the schema covers the mechanics. The description still adds real meaning: what each plan costs and how long it lasts, which the schema does not state.

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?

Opens with a specific verb and resource ("Buy a pass for the funding feed") and immediately enumerates the two plans with their exact prices. An agent can tell this apart from funding_rates, which simply consumes the resulting token.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete breakeven thresholds against the pay-per-call alternative ($0.002/call): worth it above ~125 calls/day for 24h and ~72 calls/day for 7d. It also states where to go next, naming arguments.pass of funding_rates and the Authorization bearer header for direct HTTP calls.

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