Skip to main content
Glama

book_stats

Read-only

FREE, no key: the Taifoon venue's 24 h statistics for one market as the venue computes them: volume, quote volume, trade and fill counts, high, low, open, close, change in percent, and the venue clock with the reading's age. Venue figures (test money, synthetic actors), never an exchange's: say 'venue book'.

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": {
      "market": "<market>"
    },
    "name": "book_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
marketYesthe market

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive/non-idempotent, so the safety profile is covered; the description goes further by disclosing that figures are venue-computed against test money and synthetic actors rather than a real exchange, and that the reading carries an age. That provenance and staleness caveat is exactly the context an agent would otherwise get wrong, and it is consistent with idempotentHint=false (a rolling 24 h window returns different values per call). It stops short of noting rate limits or result-shape caveats.

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 dense sentences with the price/auth qualifier and the resource front-loaded, then the field list, then the provenance caveat. Nearly every clause earns its place, though the closing 'say venue book' instruction is stylistic rather than operational and the enumeration is packed tightly enough to slow reading.

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 no output schema, the description usefully doubles as return-value documentation by naming the metrics the agent will receive, and it covers auth, data provenance, and reading freshness. What remains thin is unit/interval detail (the exact 24 h boundary, how 'change in percent' is computed) and any indication of error behavior for an unavailable market.

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% with a single required 'market' field constrained to an enum, so the schema fully specifies the input. The description only restates that the scope is 'one market' and adds no format, case-sensitivity, or default guidance beyond it. Baseline 3 applies when the schema does the work.

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-like resource ('the Taifoon venue's 24 h statistics for one market') and then enumerates the exact contents: volume, quote volume, trade and fill counts, high, low, open, close, percent change, and venue clock. The field list separates it from siblings like book_depth and book_fills without needing to name them, and 'as the venue computes them' fixes the source of truth.

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?

'FREE, no key' tells the agent there is no auth prerequisite, which is genuine usage context. However, there is no explicit statement of when to prefer this over book_depth, book_fills, or price, and no exclusion or precondition beyond the single required market. Usage is implied by the field list rather than guided.

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