Skip to main content
Glama

Get funding rates

get_funding_rates
Read-only

Funding rates for one symbol across exchanges, with open interest, long/short ratio, large positions and liquidations, from Otto AI. Use to compare venues or gauge positioning. Paid per call from your key's SingIt limits in USDC; Base accounts only for now.

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

Input Schema

NameRequiredDescriptionDefault
symbolYesMarket ticker, e.g. BTC, ETH, SOL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses the two things an agent most needs and cannot get from structured fields: the call is paid per call against SingIt limits in USDC, and it is currently Base accounts only. It also lists the data payload returned, which is valuable given there is 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.

Conciseness4/5

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

Two sentences, front-loaded with what the tool returns before the usage hint and the cost/account caveats. The middle clause packs five data types into one sentence but does so without wasted words.

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 read tool with no output schema, the definition covers purpose, return contents, cost model, and account eligibility. Only minor things like error behavior or rate granularity are absent, and those are low stakes here.

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 100% and the single parameter already documents itself with examples (BTC, ETH, SOL). The description only reinforces that it takes exactly one symbol rather than a list, adding marginal meaning beyond 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 specifically (funding rates for one symbol across exchanges) and enumerates the co-returned data: open interest, long/short ratio, large positions, liquidations. That is enough to separate it from get_price or get_token_price, though it never explicitly contrasts itself with those siblings.

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?

"Use to compare venues or gauge positioning" gives a clear intent-based trigger for reaching for this tool. There is no explicit when-not or named alternative, so an agent must infer that plain spot pricing belongs to get_price.

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.