Skip to main content
Glama

Funding history

funding_history
Read-only

Funding rate history of one contract over up to 30 days, with latest, average, min, max and average APR.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "funding_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
symbolYesCoin of a USDT perpetual contract, e.g. BTC, ETH, SOL (BTCUSDT also works).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds useful behavioral context by stating the 30-day maximum window and listing the summary metrics returned (latest, average, min, max, average APR), which partially compensates for the absence of an 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?

The description is a single, front-loaded sentence with zero wasted words. The essential scope and return metrics appear immediately, making it easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool named funding_history with no output schema, the description lists summary metrics but leaves a key ambiguity: whether it returns a raw time series of funding events or only aggregate statistics over the window. It also does not mention the granularity of the history, so an agent cannot fully predict the return shape.

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 coverage is 50%: the symbol parameter is well documented in the schema, while days only has min/max/default. The description's 'up to 30 days' repeats the schema maximum and 'one contract' reinforces the symbol scope, but it does not add meaningfully new semantics for either parameter.

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?

The description states a specific verb and resource: 'Funding rate history of one contract over up to 30 days.' It also names the returned metrics, making the tool's scope and output shape immediately clear 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?

Usage is implied by the purpose and the 30-day window, but there is no explicit when-to-use guidance, no exclusions, and no alternatives named. An agent can infer that this is the funding-history tool, but nothing directs it away from other market data tools for related queries.

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