Skip to main content
Glama

book_fills

Read-only

FREE, no key: the Taifoon venue's last fills for one market (newest first, up to 500): each with side, price, qty, whether the taker was the maker, and t_logical; plus the flow over them computed here: fills, taker buy qty, taker sell qty, the window in seconds, VWAP. Venue flow (synthetic makers and flow actors), never CME order flow: say 'venue book'. Attributions are the venue's anonymised ids; no person is named.

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_fills"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNofills to read (default 200)
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 read-only, open-world, non-idempotent and non-destructive, so the safety profile is covered. The description still adds real context beyond them: it is free and needs no key, results are newest-first and capped at 500, the response carries both raw prints and locally computed flow metrics, and attributions are anonymised venue ids with no person named.

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?

The lead clause front-loads the essential facts (free, no key, venue fills, one market) and the rest enumerates returned fields and aggregates. It is dense but nearly every clause carries information; the definition would gain from splitting the long run-on sentence.

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?

There is no output schema, so the description has to describe return values, and it does: side, price, qty, taker-was-maker flag, t_logical, plus the aggregate flow fields. Gaps remain around units, timestamp semantics, and behaviour when fewer than limit fills exist, but the core is covered.

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%, with the market enum and the limit bounds/default already documented in the schema, so the baseline is 3. The description only restates the cap and adds the newest-first ordering; it adds nothing about units (qty, price tick) or what t_logical means.

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 and resource: 'the Taifoon venue's last fills for one market', with ordering (newest first) and a cap (up to 500). It also explicitly marks the boundary against a different data class ('never CME order flow'), so an agent knows exactly what this 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?

Usage is implied by the data it returns (recent prints plus flow aggregates for one market), and the 'say venue book, never CME order flow' line gives an interpretation rule. However, it never says when to prefer this over adjacent tools like book_stats, digest, or price, and gives no exclusion conditions for the limit parameter.

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