Skip to main content
Glama

Microverse Market Data

Get historical order book

get_historical_book
Read-onlyIdempotent

Recorded order-book snapshots for one symbol over a time window, replayed from our raw captures. date is YYYY-MM-DD; start/end are HH:MM[:SS] US Eastern time; window up to 2 hours; interval_seconds 5..600 (one snapshot per interval); levels_per_side up to 20. Use list_history for dates and symbols.

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": {
      "venue": "<venue>",
      "symbol": "<symbol>",
      "date": "<date>",
      "start": "<start>",
      "end": "<end>"
    },
    "name": "get_historical_book"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYes
dateYes
startYes
venueYes
symbolYes
levels_per_sideNo
interval_secondsNo

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 declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds real behavioral context beyond that: the data is a replay of raw captures rather than live state, and the window/granularity limits shape how it must be called. It stops short of saying whether captures are gapless or how gaps/failures in the window are surfaced.

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?

Dense, front-loaded and free of filler: purpose first, then formats and limits, then the discovery pointer. Every clause carries a constraint or routing fact an agent would otherwise have to guess.

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 still conveys the return granularity (one snapshot per interval, up to N levels per side) well enough to plan calls. Remaining gap: the actual snapshot shape (bid/ask level fields, timestamps) and venue value space are not described anywhere the agent can see.

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 description coverage is 0%, so the description carries the full burden, and it does most of the work: date as YYYY-MM-DD, start/end as HH:MM[:SS] US Eastern, interval_seconds 5..600, levels_per_side up to 20, plus the implicit window cap. The notable gap is venue, whose accepted values are never characterized or routed (unlike symbol, which points to list_history).

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+resource+scope: recorded order-book snapshots for one symbol over a time window, replayed from raw captures. 'Recorded'/'historical' implicitly distinguishes it from the live get_order_book sibling, but that alternative is never named, so the differentiation requires inference.

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?

Gives a concrete prerequisite routing ('Use list_history for dates and symbols') and an operational constraint (window up to 2 hours, one snapshot per interval). It says nothing about when to prefer this over get_order_book or get_consolidated_book, and does not state what to do when a 2-hour window is insufficient.

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