Skip to main content
Glama

Coin snapshot

coin_snapshot
Read-only

One contract now: mark price, funding rate and APR, next funding time, open interest and its 24h change, long/short account ratios, taker buy/sell ratio, max leverage.

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

Input Schema

NameRequiredDescriptionDefault
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.8/5.0
Behavior4/5

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

Annotations already establish that this is a read-only tool and not open-world. The description adds meaningful behavioral context by clarifying that it returns a current snapshot for one contract and by listing the specific market metrics included, which helps an agent understand the scope and nature of the read.

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 compact sentence with a clear front-loaded scope statement followed by the relevant metric list. Every phrase contributes useful information, and there is no redundant wording.

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 snapshot tool with read-only annotations and no output schema, the description gives enough context to invoke it correctly and understand what data it returns. It could be slightly more complete by mentioning refresh or latency characteristics, but those gaps are minor.

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 description coverage is 100%, and the symbol parameter is already documented with examples and the BTCUSDT alternative. The description confirms the single-contract scope but does not add further semantics beyond what the schema provides, so baseline 3 is appropriate.

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 clearly identifies a current per-contract snapshot and enumerates the metrics returned, including mark price, funding, open interest, ratios, and leverage. It is specific enough to distinguish a point-in-time contract snapshot from historical tools such as funding_history, though it does not name alternatives explicitly.

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?

The phrase "One contract now" implies this is for a current single-contract snapshot rather than historical or multi-market data. However, it does not explicitly state when to use this tool versus siblings like funding_history or market_overview, so guidance is implied rather than spelled out.

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