Skip to main content
Glama

Read the Exchange’s depth for one instrument

book
Read-onlyIdempotent

The Exchange’s depth for one instrument: key is cardId|finish (tally|standard), share: or lot:.

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": {
      "key": "<key>"
    },
    "name": "book"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesthe instrument to read: a card as cardId|finish (for example tally|standard), a company’s share as share:<company>, or a lot as lot:<id>

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / key / description
      Added value: +"the instrument to read: a card as cardId|finish (for example tally|standard), a company’s share as share:<company>, or a lot as lot:<id>"
  2. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds no behavioral context beyond that — nothing about what 'depth' contains, whether it is a live snapshot, or how the three key forms (card / share / lot) behave differently.

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 compact sentence with the key formats front-loaded and no filler. It is short and scannable, though it spends its words duplicating the title and schema rather than adding information.

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

Completeness2/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 carries the burden of explaining what is returned — price levels, quantities, sides, or freshness. It never does, leaving a read tool whose output shape ('depth') is undefined for the caller.

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 parameter's schema text is a near-verbatim copy of the description, so the description adds no meaning beyond the schema. Baseline 3 applies; it does not clarify what 'finish' values (tally/standard) actually denote or the lot id format.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description's first clause repeats the title verbatim ('The Exchange's depth for one instrument') without a verb like read/fetch or an explanation of what 'depth' means (order book levels? counts?). Beyond the title it only supplies the key format, so an agent learns almost nothing about the operation itself and nothing that distinguishes it from siblings like table_state or bureau_look.

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

Usage Guidelines2/5

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

No when-to-use guidance, no prerequisites, and no mention of any alternative tool or condition under which another tool (e.g. find_table, table_state) should be preferred. Usage must be inferred entirely from the name and title.

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