Skip to main content
Glama

funding_rates__funding

Current funding rate per symbol across venues, with annualized rate and carry_play block. Price: $0.01 per call in USDC on Base (eip155:8453), paid with x402 in params._meta["x402/payment"]. HTTP: GET https://api.firstmention.uk/s/funding-rates/funding

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

Input Schema

NameRequiredDescriptionDefault
symbolsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / symbol
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / symbols
      Added value: +{
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • removedInput schema / properties / symbol / description
      Removed value: -"Asset symbol, e.g. BTC"
    • removedInput schema / required
      Removed value: -[
      -  "symbol"
      -]
  3. Changed3 schema fields changed
    • addedInput schema / properties / symbol
      Added value: +{
      +  "description": "Asset symbol, e.g. BTC",
      +  "type": "string"
      +}
    • removedInput schema / properties / symbols
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / required
      Added value: +[
      +  "symbol"
      +]
  4. Changed4 schema fields changed
    • removedInput schema / properties / assets
      Removed value: -{
      -  "description": "Alias for symbols",
      -  "type": "string"
      -}
    • removedInput schema / properties / symbol
      Removed value: -{
      -  "description": "Single perpetual symbol, e.g. BTC",
      -  "type": "string"
      -}
    • removedInput schema / properties / symbols / description
      Removed value: -"Comma separated symbols, max 10 (/batch) or 25 (/spread)"
    • removedInput schema / required
      Removed value: -[
      -  "symbols"
      -]
  5. Changed4 schema fields changed
    • addedInput schema / properties / assets
      Added value: +{
      +  "description": "Alias for symbols",
      +  "type": "string"
      +}
    • changedInput schema / properties / symbol / description
      Previous value: -"Perpetual symbol, e.g. BTC or ETH"New value: +"Single perpetual symbol, e.g. BTC"
    • changedInput schema / properties / symbols / description
      Previous value: -"For /batch: comma separated symbols, max 10"New value: +"Comma separated symbols, max 10 (/batch) or 25 (/spread)"
    • changedInput schema / required
      Previous value: -[
      -  "symbol"
      -]New value: +[
      +  "symbols"
      +]
  6. Changed2 schema fields changed
    • changedInput schema / properties / symbol / description
      Previous value: -"Asset symbol, e.g. BTC"New value: +"Perpetual symbol, e.g. BTC or ETH"
    • addedInput schema / properties / symbols
      Added value: +{
      +  "description": "For /batch: comma separated symbols, max 10",
      +  "type": "string"
      +}
  7. First observed

TDQS

B3.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does real work: it discloses the paid nature ($0.01 per call in USDC on Base, eip155:8453), the x402 payment location (params._meta["x402/payment"]), and the HTTP endpoint. It does not cover which venues are aggregated or how fresh the rates are.

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 the core capability, with payment and transport details appended. Dense but every element is operationally relevant; no filler.

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 simple one-parameter tool the description covers capability, return fields, pricing, and transport, which is solid. It still leaves the default behavior without a symbol argument and the venue coverage unspecified, which matter for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter 'symbols' has 0% schema description coverage and the description does not compensate — it never says whether the value is a single ticker or a comma-separated list, nor what happens when it is omitted (the parameter is not required, so it presumably defaults to all symbols, but that is unstated).

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?

States a specific verb and resource — current funding rate per symbol across venues — and names the payload extras (annualized rate, carry_play block). It does not, however, distinguish itself from close siblings like funding_rates__batch, funding_rates__carry, or fundinglens__rates, so an agent cannot tell from the description alone which to pick.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no exclusions, and no named alternative despite several tightly related siblings (batch, carry, spread, watch, fundinglens__rates). The only usage signal is the implicit 'per symbol' scoping.

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