Skip to main content
Glama
zenith-sb-mcp

zenith-sb-mcp

trade_book

Read-only

Retrieve traded volume broken down by price level for the current IDX session, with optional big-money filtering and auction-phase exclusion to isolate the real distribution.

Instructions

Traded volume broken down by price level for a session. mode=BIG_MONEY restricts to large prints, mode=OVERALL covers everything; omitted sends no mode. data_modes excludes auction phases: EXCLUDE_PRE drops the pre-opening auction, EXCLUDE_POST the post-closing one. Both auctions match at a single price and can distort the distribution badly, so excluding them changes the picture rather than trimming it. chart=true reads a different endpoint returning the chart form of the same idea, not a rendering of this one. group_by is REQUIRED: without it every call answers 400 "Group by is required" whatever else is sent, which is why this tool could not be called at all until the parameter existed. PASS group_by=1 — measured 2026-09-01, that returns the by-price book this tool is named for. 2 is also accepted but answered empty on a closed market, so what it groups by is not established; 0 is read as absent and 3 is refused. Only those four have been tried, so your value is sent verbatim rather than checked against a list. chart=true is a different endpoint and has never been seen to demand it, so it is not required there. An empty result is normal before the session's first print. It is a per-session view: there is no date argument, so this is today. PENDING VERIFICATION, and precisely which part: the RESPONSE has now been seen live — a book of price levels, each with buy/sell/pre_open/post_close/total blocks — but mode and data_modes have never been observed to be accepted, because until group_by existed no call from this project ever reached this endpoint at all. Treat those two as unverified guesses and check the payload rather than assuming a filter was applied.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "trade_book"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoOVERALL or BIG_MONEY. Omitted sends no mode.
chartNoRead the chart endpoint instead of the table.
limitNoMax rows. Omitted takes the server default.
symbolNoIDX ticker. Omit for whatever the endpoint returns market-wide.
group_byNoREQUIRED. Use 1 for the by-price book; 2 is accepted, 3 is refused. Sent verbatim.
data_modesNoAuction phases to exclude: EXCLUDE_PRE and/or EXCLUDE_POST.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only cover read-only/open-world safety, and the description goes well beyond them: a hard 400 error without group_by, group_by values sent verbatim rather than validated, per-session/today-only semantics with no date argument, and an explicit note that mode and data_modes remain unverified guesses. It even describes the response shape (`book` of price levels with buy/sell/pre_open/post_close/total blocks) — unusual candor for a tool with no output schema.

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 and the mode/data_modes options before the long group_by caveat, and nearly every sentence carries operational value. It is nonetheless long and somewhat discursive, with the group_by requirement restated in the chart caveat and the verification caveat repeated at both parameter and response level.

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?

For a six-parameter, no-output-schema tool this covers usage, failure modes, verification status and return shape thoroughly. The one gap is that the relationship to obvious siblings (orderbook, running_trade, intraday_prices) is never stated, leaving the agent to infer which volume view to pick.

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

Parameters5/5

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

Schema coverage is already 100%, but the description adds meaning the schema cannot: group_by=1 yields the by-price book, 2 is accepted but answered empty (grouping semantics unknown), 0 is read as absent, 3 is refused, and values are not validated against a list. It likewise warns that mode/data_modes acceptance has never been observed, telling the agent to inspect the payload rather than assume filtering happened.

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?

Opens with a precise verb+resource+scope: 'Traded volume broken down by price level for a session.' It also clarifies that chart=true reaches a different endpoint rather than a rendering of this one, which prevents a common misuse. It does not explicitly name a sibling (e.g. orderbook, running_trade, chart_series) it competes with, so it falls short of full sibling differentiation.

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?

Explicitly states when to use each parameterization: mode=BIG_MONEY vs OVERALL, omitting mode sends nothing, data_modes excludes specific auctions and why that materially changes the distribution. It also calls out that chart=true is a different endpoint with different requirements, and that empty results are normal before the first print.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.