Skip to main content
Glama

Market snapshot

market_snapshot
Read-only

Live snapshot of a crypto pair on liquidmap: price, 24 h change, the largest resting bid and ask walls near the price, big aggressive trades ("bursts") of the last hour, today's CVD (spot and perpetual) and futures funding and open interest. Start here.

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": {
      "pair": "<pair>"
    },
    "name": "market_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
pairYesCoin traded against USDT: BTC, ETH, SOL, XRP, BNB, DOGE, ZEC or NEAR

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds that the data is 'live' and scopes the windows (24h change, last hour of bursts, today's CVD), which is genuine behavioral context. It says nothing about freshness/latency, rate limits, or what happens for thin markets where walls or bursts may be absent.

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?

One dense sentence, front-loaded with the core purpose before the field enumeration, followed by a short call-to-action. The field list is long but each item conveys distinct payload content that helps an agent decide to call it.

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?

With one required parameter and no output schema, the description usefully substitutes by enumerating the returned data categories, which is exactly what an agent needs to judge relevance. Missing only edge-case behavior (empty walls/bursts, timestamp of the snapshot).

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 'pair' parameter has an explicit enum with a description, so the schema carries the load. The description only says 'crypto pair' and does not restate the supported coins or clarify the USDT quote convention, adding little 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?

States a specific verb and resource ('Live snapshot of a crypto pair on liquidmap') and enumerates the payload categories, so the agent knows exactly what comes back. It does not differentiate itself from siblings like cvd, futures, big_trades or order_book_walls, even though several of those fields overlap with what this snapshot returns.

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?

'Start here' signals this is the default entry point, which is useful directional guidance. However, it never says when to prefer the narrower siblings (cvd, futures, big_trades, order_book_walls) over this broad call, so the routing logic is only implied.

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