Skip to main content
Glama
Sign In

Crypto Market

by io.github.gojisatoshi888
OverviewDiscussionsAdmin

funding_rates

Perpetual futures funding rates. Pass tickers such as BTC,ETH,SOL. Tries Binance, then Bybit, then OKX, and reports which source answered. Paid tool: $0.005 USDC per call via x402 on eip155:8453. The first few calls each UTC day are free; after that an unpaid call returns PaymentRequired and does not charge.

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_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsNoBTC,ETH,SOL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 behavioral burden, and it does well: it discloses the source failover order (Binance, then Bybit, then OKX), that the answering source is reported, the per-call price of $0.005 USDC on eip155:8453, and the free-calls-per-UTC-day policy with non-charging PaymentRequired failures. It does not describe the shape or units of the returned funding-rate data, leaving a meaningful gap for a tool with no annotations and no output schema.

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?

Four short sentences, front-loaded with purpose, then input format, then source failover, then the payment model — every sentence carries information an agent needs before calling. No redundant restatement of the name 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?

For a one-parameter tool with no annotations and no output schema, the description covers invocation, cost, quota, error behavior, and data provenance. The main omission is return-value content (which funding-rate fields, units, or per-symbol structure), which the missing output schema forces the description to leave unexplained.

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?

With only 0% schema description coverage, the description must compensate for the single symbols parameter, and it does by explaining the comma-separated ticker format and giving concrete examples. It does not state limits on how many symbols may be passed or what happens with unknown tickers.

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 specific resource (perpetual futures funding rates) and shows the input format with example tickers (BTC,ETH,SOL), which is distinct from siblings like get_price or top_movers. It does not explicitly contrast itself with those siblings, but the purpose is unambiguous.

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?

It clearly states how to invoke the tool and describes the payment/free-tier flow, including that an unpaid call returns PaymentRequired and is not charged. It lacks an explicit statement of when to prefer this over a sibling like get_price, which keeps it from a 5.

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

All Crypto Market 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