Skip to main content
Glama

funding snapshot

funding-snapshot
Read-onlyIdempotent

Perp funding of a coin now on bitget, gate, kucoin, okx: rate, interval, annualized, mark/index basis where published, cross-venue spread. Market data only Price: $0.005 per call, USDC on Base via x402.

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": {
      "coin": "<coin>"
    },
    "name": "funding-snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinYesstring, e.g. SOL

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 cover read-only, idempotent, non-destructive and open-world behavior, so the bar is lower. The description nevertheless adds material context the annotations cannot convey: this is a paid call at $0.005 per call settled in USDC on Base via x402, which an agent must know before invoking. It stops short of describing behavior when a venue does not publish a field or does not list the coin.

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 compact sentences, front-loaded with what the tool returns, then the pricing constraint. The field list is dense but each item is informative; the only friction is the telegraphic register ('now on bitget, gate, kucoin, okx').

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?

There is no output schema, so the description carries the burden of describing returns — and it does, naming each returned field including the conditional 'mark/index basis where published'. Given one required parameter and full annotation coverage, the only gap is failure behavior for an unlisted coin or unsupported venue.

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?

There is a single parameter with 100% schema description coverage ('string, e.g. SOL'), so the schema already carries its meaning. The description only restates 'of a coin' and adds no format, casing, or symbol-resolution detail beyond the schema example.

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?

States a specific verb+resource (perp funding of a coin) and then enumerates exactly what is returned: rate, interval, annualized, mark/index basis where published, cross-venue spread across bitget, gate, kucoin, okx. No sibling tool covers funding data, so an agent can route to this one from the description alone 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 rather than stated: the venue list and 'cross-venue spread' make clear this is for comparing perp funding across exchanges, and 'Market data only' rules out execution-type intents. However, no alternative sibling is named and no when-not condition (e.g. unlisted coin, unsupported venue) is given.

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