Skip to main content
Glama

funding_rates__batch

Batch funding lookup for up to 10 symbols in one paid call. 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/batch

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

Input Schema

NameRequiredDescriptionDefault
symbolsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / symbols / description
      Removed value: -"Comma-separated symbols, up to 10"
    • removedInput schema / required
      Removed value: -[
      -  "symbols"
      -]
  2. Changed2 schema fields changed
    • addedInput schema / properties / symbols / description
      Added value: +"Comma-separated symbols, up to 10"
    • addedInput schema / required
      Added value: +[
      +  "symbols"
      +]
  3. 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"
      -]
  4. 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"
      +]
  5. 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"
      +}
  6. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does a good job on the unusual parts: it discloses that the call is paid ($0.01 USDC on Base, eip155:8453), where the x402 payment token goes (params._meta["x402/payment"]), and the raw HTTP endpoint. It omits failure modes (what happens when payment is missing or >10 symbols are passed), which holds it to a 4.

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?

Two sentences, front-loaded with purpose and capacity, then the payment mechanics and endpoint. No filler; every clause carries an operational fact the agent needs.

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?

There is no output schema, so the description should hint at what comes back (per-symbol rate, venue, timestamp), and it does not. Payment and capacity are fully covered, but the response shape and the symbol-string format are gaps for a paid tool an agent must call blind.

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 0% and the single `symbols` param is an untyped-in-practice string with no explanation. The description adds real value by capping the list at 10 symbols, but it never states the expected encoding (comma-separated, space-delimited, or repeated), which is essential for a string-typed list parameter.

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 states a specific verb and resource — batch funding-rate lookup — plus the hard scope limit of 'up to 10 symbols in one paid call'. The word 'batch' differentiates it from single-symbol siblings like funding_rates__funding, but that sibling is never named, so the contrast is only implicit.

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 'batch' and by the cost framing ('one paid call'), so an agent can infer it should batch rather than call repeatedly. There is no explicit when-to-use statement, no named alternative for a single symbol, and no guidance on splitting larger symbol lists.

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