Skip to main content
Glama

The Coin Daily Research

Show order-book liquidity

research_show_liquidity
Read-onlyIdempotent

Display a focused order-book liquidity widget after evidence from research_read_series is available. Displayed bid/ask depth or quoted spread. Depth and spread use separate scales, not a misleading combined axis. Use only when a visual helps answer the question. Not a data fetch, calculation, navigation hub or replacement for the assistant's interpretation. Reuses captured source numbers and selection; expired evidence requires an explicit new read.

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": {
      "evidence_id": "<evidence_id>"
    },
    "name": "research_show_liquidity"
  }
}

Input Schema

NameRequiredDescriptionDefault
evidence_idYesExact evidence.id from the matching data tool in this authenticated conversation. The server retrieves original values and selection; do not supply chart numbers.

Output Schema

NameRequiredDescriptionDefault
factsNo
statusYes
messageNo
surfaceYes
evidenceNo
selectionYes
research_urlYes
schema_versionNotcd.mcp-research/v2
retry_after_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description still adds non-obvious behavior: values are captured (not recomputed), the widget reuses the prior selection, expired evidence requires an explicit re-read, and depth vs spread are rendered on separate scales rather than a combined axis. Those are real operational facts an agent could not infer from the annotations.

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?

Front-loaded with purpose, then prerequisite, then exclusions. Six short sentences, nearly all load-bearing; the separate-scales remark is slightly editorial but still prevents a real misreading of the output.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Single-parameter tool with rich annotations and an output schema, so the description needn't explain return shape. It covers the prerequisite, the display semantics, the evidence-expiry edge case, and the boundary against data-fetch siblings — nothing an agent needs in order to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100% and the evidence_id description already explains the 64-hex id source, so the baseline is 3. The description adds lifecycle meaning the schema omits: evidence expires, and supplying chart numbers is not accepted ('reuses captured source numbers and selection'). Useful, but limited to one parameter.

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 (Display) and resource (order-book liquidity widget), then narrows it to the two things rendered: bid/ask depth or quoted spread. That distinguishes it from the other display siblings (research_show_price, research_show_open_interest, research_show_volume-style tools) without needing to open any schema.

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

Usage Guidelines5/5

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

Explicit prerequisite ('after evidence from research_read_series is available'), explicit selection rule ('Use only when a visual helps answer the question'), and explicit exclusions ('Not a data fetch, calculation, navigation hub or replacement for the assistant's interpretation'). The alternative path for raw numbers is effectively named.

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