Skip to main content
Glama
zenith-sb-mcp

zenith-sb-mcp

orderbook

Read-only

Retrieve a symbol's full IDX bid/offer depth ladder, including per-board market data and foreign flow fields, to inspect liquidity and price levels.

Instructions

Full order-book depth ladder for a symbol. UNITS, AND THEY ARE MIXED IN ONE RESPONSE. volume here is SHARES (e.g. 3,545,526,000) while technicals' volumeLots for the same symbol and session is LOTS (35,488,071). They reconcile at exactly 100 shares per lot — the IDX lot size — and neither figure is wrong. Worse, this same payload labels its total_bid_offer depth figures lot while carrying volume in shares a few keys away. Two units under similar names in one response is a silent-wrong-answer generator: check which one you are holding before comparing anything, and never compare volume here against volumeLots there without the ×100. market_data[] carries the per-board split (All Market / Regular / Nego / Cash). It is also also presented by price_market, with optional board filtering and an explicit orderbook source. FOREIGN FLOW HAS NO DATE ON THIS PAYLOAD. fbuy/fsell/fnet arrive with nothing saying which session they are from, and foreign flow publishes at roughly 18:00 WIB, so before that release they are the PREVIOUS session's. price_bands surfaces this as an explicitly null dataAsOf with a note; market_movers carries the date for real as foreign.sessionDate.

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": {
      "symbol": "<symbol>"
    },
    "name": "orderbook"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesIDX ticker

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description focuses on the traps instead: volume is in shares while technicals' volumeLots is in lots, total_bid_offer is labeled 'lot' but sits beside share-denominated volume, and fbuy/fsell/fnet carry no session date and lag until ~18:00 WIB. These are genuinely non-obvious, high-value disclosures that prevent silent wrong answers. It loses a point because the payload structure itself (bid/ask level arrays, ordering) is only partially sketched rather than described.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The lead sentence is correctly front-loaded, but the body is rambling, switches to ALL-CAPS emphasis, repeats itself ('It is also also presented'), and embeds long illustrative numbers that add bulk rather than clarity. Much of the content does earn its place as correctness warnings, but the same information could be delivered in roughly half the words with tighter structure.

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

Completeness3/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 must carry the return-value burden, and it does cover the highest-risk elements (units, board split, undated foreign flow). However, the core deliverable — the actual depth ladder of bid/ask price levels — is never described, leaving an agent unsure what the primary payload looks like. Adequate for the gotchas, incomplete for the shape of the response.

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?

There is a single parameter, symbol, with 100% schema description coverage ('IDX ticker'), so the schema already carries the semantics. The description adds nothing new about the parameter, which is acceptable at this coverage level. Baseline 3 applies.

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 specific verb-and-resource statement: 'Full order-book depth ladder for a symbol,' which tells an agent exactly what is returned. It also distinguishes itself from price_market by noting that market_data[] is 'also presented by price_market, with optional board filtering,' which implies the sibling's added capability. It stops short of a crisp one-line differentiation, since the purpose sentence is immediately buried under unit caveats.

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?

The mention of price_market with 'optional board filtering and an explicit orderbook source' hints at an alternative, but never states the selection rule ('use X when you need Y'). There is implicit guidance about checking units and dates before comparing values, which is conditional usage advice. No exclusions, prerequisites, or explicit when-not-to-use guidance are given.

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