Skip to main content
Glama
zenith-sb-mcp

zenith-sb-mcp

broker_summary

Read-only

Retrieves which IDX brokers net-bought or net-sold a stock in lots and IDR value, with foreign, local or government classification, across the latest session, presets or a date range.

Instructions

Broker summary for an IDX stock: which brokers net-bought/sold, in lots and IDR value, with foreign/local/govt classification. This is the core bandarmology signal — TradingView has no equivalent. DATES: omit from/to for the latest completed session. Supply BOTH from and to (YYYY-MM-DD) for a historical window — the server aggregates net flow across it in one request, so a multi-month range is as cheap as one day. For a single past day pass the same date twice. Both ends are required; a half-specified range is rejected because the API would silently return the latest session instead. An empty result for a weekend or public holiday is expected, not an error. SIGNS: sell-side rows carry NEGATIVE netLots and netValueIdr, because that is how Stockbit sends them. Do not negate them again. A row omits netLots or netValueIdr when that figure could not be read — missing on the wire, empty, or in a format this server refuses to guess at. Absent is NOT zero, it means unknown, so do not sum these rows without checking. unreadable on the envelope names the wire keys and counts, per side, how many listed brokers a total over these rows would miss. resolve_names: true adds the securities house to each row as name, joining against the brokers directory so you do not have to. The directory is cached for five minutes, so this is usually free. It is best-effort: if the directory cannot be read the rows and every figure on them are unchanged and names.note says why, and a code the directory does not carry simply has no name — an unresolved code is not a nameless broker.

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": "broker_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoRange end, YYYY-MM-DD (inclusive). Requires `from`.
fromNoRange start, YYYY-MM-DD. Requires `to`.
limitNoMax brokers per side (default 50; API default 25 truncates)
periodNoPreset window instead of from/to — LATEST (default), YESTERDAY, LAST_7_DAYS, LAST_3_MONTHS, YEAR_TO_DATE. The server aggregates the whole window in ONE request, so YEAR_TO_DATE costs the same as today. Ignored when from/to are given.
symbolYesIDX ticker, e.g. BBRI
date_toNoAlias for `to`.
end_dateNoAlias for `to`.
date_fromNoAlias for `from`.
start_dateNoAlias for `from`.
market_boardNoDefault REGULER — the ordinary order book, and what bandarmology means. ALL folds in negotiated blocks and can be several times larger. NEGO and TUNAI select those boards alone.
investor_typeNoDefault ALL
resolve_namesNoAdd each broker's securities house as `name`, joined from the cached directory.
transaction_typeNoNET (default) nets each broker's buys against its sells; GROSS does not.

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 supply readOnly/openWorld/non-destructive; the description goes far beyond with sell-side rows carrying negative netLots/netValueIdr that must not be re-negated, absent fields meaning unknown rather than zero, the `unreadable` envelope naming unread wire keys, and resolve_names being a cached five-minute best-effort join whose failure leaves figures unchanged. These are exactly the failure modes an agent would otherwise misread.

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, then split into DATES and SIGNS blocks plus a resolve_names paragraph, so an agent can scan to the section it needs. It is long, and the resolve_names paragraph partly restates the schema's own 'joined from the cached directory' wording, but every sentence conveys a non-obvious constraint rather than filler.

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

Completeness5/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 carries the return-value burden and does so: it explains the per-row netLots/netValueIdr fields, their sign convention, when they are absent, what the `unreadable` envelope counts, and how `names.note` reports a failed join. For a 13-parameter aggregation tool this is enough to call and interpret it correctly.

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 coverage is 100%, so baseline is 3, but the description adds real meaning beyond it: why both range ends are mandatory (the API would silently return the latest session otherwise), the equivalent-cost framing for multi-month ranges, and the best-effort/caching semantics of resolve_names. The remaining parameters (limit, market_board, investor_type, transaction_type) are left entirely to the schema, which is already detailed.

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?

The opening sentence names a specific verb and resource – 'which brokers net-bought/sold, in lots and IDR value, with foreign/local/govt classification' – for one instrument type (IDX stock). The 'core bandarmology signal' framing and the explicit note that TradingView has no equivalent carve out a distinct niche, so an agent won't confuse it with orderbook or running_trade.

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

Usage Guidelines4/5

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

Strong operational guidance: omit from/to for the latest session, pass both for a window, pass the same date twice for one past day, and an explicit warning that a half-specified range is rejected. Also states an empty result on weekends/holidays is expected, not an error. It does not name sibling tools or say when to prefer this over them, so it falls short of a 5.

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