Skip to main content
Glama
zenith-sb-mcp

zenith-sb-mcp

running_trade

Read-only

Read the IDX running trade tape print by print or grouped, filtered by ticker and buy/sell side, to inspect intraday trades from the session open.

Instructions

The running-trade tape: individual prints as they cross the exchange. Omit symbol for the market-wide tape, pass it to follow one ticker. action filters to one side (BUY = buyer-initiated, SELL = seller-initiated); omitted means the endpoint's own default, which is not necessarily ALL. grouped=true reads a different endpoint that returns the tape aggregated rather than print by print. It is not a display option: the two return different payloads. WHICH SESSION AM I LOOKING AT. Both views carry data.date and it is the answer — read it rather than assuming today. Measured 2026-09-01 after the ~18:00 WIB broker release, both served that same day. Broker-derived and foreign-derived figures across this API publish at roughly 18:00 WIB, so before that release a payload carrying YESTERDAY's date is correct and not yet published — it is not stale data and not a bug. market_movers' foreign.isShown is the explicit flag for the same thing and flips false to true across that release. INTRADAY BROKER ATTRIBUTION DOES NOT EXIST TO BE RETURNED. IDX closed broker codes on live running trade on 6 December 2021. So is_broker_exists: false with empty buyer/seller is an honest answer about the exchange, not a parse failure or a missing field — check that flag per row rather than concluding the projection broke. THIS TAPE IS NOT LIVE. Measured against the live API during an open session, it runs about EIGHT TO TEN MINUTES BEHIND and refreshes in bursts — its head sat unchanged for over three minutes while the lag grew second for second, and the staleness is at Stockbit's origin, not in a CDN. Do not answer 'what just traded' from it. src/live/tape.ts exists because of this. READ THIS BEFORE ASKING IT ABOUT THE CLOSE. Measured 2026-08-28: the window always starts at the SESSION OPEN, at most 100 rows come back however large limit is, and offset/page are accepted but move nothing. So on a busy ticker this tool can only ever show the first 100 prints of the day — the last trade before the close is NOT reachable through it at any argument. A limit above 100 is refused here rather than silently truncated. For the rest of the session use broker_flow_intraday, which covers 09:00 to 16:14 at one-minute resolution with per-broker value and volume — but note it serves the PREVIOUS session until the ~18:00 WIB broker release, so it does not answer 'what just traded' either. NOTHING here does; docs/LIVENESS.md is the one place that says what each source is worth and why. order_by is required upstream and is NOT a time ordering: 1 is chronological from the open with real trade sizes, 2 and 3 both return lot-ascending rows that were every one a 1-lot trade when measured. None of the three returns the most recent prints and none returns the largest. 1 is the default because it is the only one that answers a question anyone asks. An empty result is NORMAL outside 09:00-16:00 WIB — the tape is a live feed and nothing crosses when the market is shut. Call market_session before treating emptiness as a fault. PENDING VERIFICATION: this response shape has not been observed live.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows, 1-100. Larger is refused: the endpoint ignores it.
actionNoALL, BUY or SELL. Omitted sends no filter.
symbolNoIDX ticker. Omit for the market-wide tape.
groupedNoRead the aggregated view instead of the print-by-print tape.
order_byNo1 chronological from the open (default), 2 and 3 lot-ascending. Not a time ordering.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare a safe read (readOnlyHint true, destructiveHint false), but the description adds genuinely behavioral facts an agent could not otherwise know: roughly 8-10 minute origin-side lag, a hard 100-row ceiling anchored at the session open, offset/page being accepted but inert, and refusals above limit=100. It also preempts two false-fault interpretations (is_broker_exists false, empty results outside 09:00-16:00 WIB).

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?

Front-loaded with the actionable core, and the all-caps headers make it scannable, but it runs well past what a 5-parameter read tool needs. The ~18:00 WIB release is explained three times, and dated measurement anecdotes plus references to src/live/tape.ts and docs/LIVENESS.md are maintenance context rather than call-time guidance.

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-shape burden and does so: data.date as the session answer, per-row is_broker_exists with empty buyer/seller, and the pending-verification caveat on the response shape. For a capped, lagged, session-bound tape, nothing an agent needs in order to interpret a result is missing.

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 the baseline is 3, but the description adds meaning beyond it: the omitted `action` default is 'not necessarily ALL', `grouped` changes payloads rather than display, and `order_by` values 2 and 3 were empirically lot-ascending rows that were all 1-lot trades. The only muddle is the limit wording, which both says 'refused here rather than silently truncated' and 'at most 100 rows come back however large limit is'.

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?

Opens with a concrete verb and resource: 'individual prints as they cross the exchange', and immediately distinguishes the two payload shapes ('grouped=true reads a different endpoint ... the two return different payloads'). An agent can tell this is the raw trade tape, not an aggregate, without opening the schema.

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 scopes when to use and when not to: 'Do not answer what just traded from it', route the rest of the session to broker_flow_intraday, route emptiness checks to market_session, and route the foreign-flag question to market_movers. It also names the condition that selects each alternative rather than leaving inference.

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