Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Running trade

flow_running_trade
Read-onlyIdempotent

Fetch every matched stock trade newest-first for one or more symbols or the whole market, filtered by price, lot size, value, time window, broker or investor type, with cursor paging.

Instructions

The tape: every matched trade, newest first, for one or more symbols or the whole market. Filter by price, lot size, value, time range, broker or investor type; page with trade_number and cursor_direction.

Volumes (lot, blot, slot) are in lots of 100 shares; values are IDR. While the market is open Stockbit hides the broker codes of today's trades (is_show_bs false) and ignores broker/investor filters; they work after the close or for a past date. A past date works for a single symbol only. Buyer/seller codes carry [D] domestic or [F] foreign.

Returns (Stockbit's data field): data{is_open_market, is_show_bs, break_time_left_seconds, date, running_trade[{id, time 'HH:mm:ss', action 'buy'|'sell', code, price(str IDR), change '-5.11%', lot(str, LOTS), value{raw IDR, formatted}, buyer 'CC [D]', seller 'XL [D]', buyer_type/seller_type BROKER_TYPE_{LOCAL,FOREIGN,GOVERNMENT,UNSPECIFIED}, is_broker_exists, market_board 'RG'|'TN'|'NG', trade_number, buy_order_number, sell_order_number, group_order_number}]}. While market is open (HAR 2026-08-24 11:25) is_show_bs=false and buyer/seller are '' (broker codes hidden live). error_type NOT_FOUND = empty page.

Endpoint: GET exodus /order-trade/running-trade.

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

Input Schema

NameRequiredDescriptionDefault
dateNoHistory date; UI only sends for a single symbol and not today ('Running Trade History Only Available for a Single Stock').
sortNoHAR always DESC; desktop store keeps 'desc' lowercase (server seems case-insensitive). Default "DESC".
limitNoPage size. Store default 50; stock-detail/fast-trade use 80 (RUNNING_TRADE_PAGE_LIMIT). limit=0 is used as a cheap market-status probe. Default 50.
symbolsNoTicker filter, repeated key. Desktop serializes `symbols=X&symbols=Y` (axios indexes:null); web HAR shows `symbols[]=X`. Omit for all stocks.
order_byNoSort column. Default "RUNNING_TRADE_ORDER_BY_TIME".
value_toNoMax trade value. Seen only in web HAR, not built by desktop code. Unit: IDR.
broker_buyNoBuyer broker code. UI only sends it for a past date or when market closed. Unit: broker code.
value_fromNoMinimum trade value. UI chips: 1e8,2.5e8,5e8,1e9,5e9 (max 1e14). Unit: IDR.
action_typeNoAggressor side filter. Default "RUNNING_TRADE_ACTION_TYPE_ALL".
broker_sellNoSeller broker code. Same restriction as broker_buy. Unit: broker code.
minimum_lotNoMinimum trade size in lots. Unit: lots.
group_actionNoSide of the order drill-down; when set the action/price/... filters are dropped.
market_boardNoBoard filter (BOARD_TYPE_* family). Default "BOARD_TYPE_ALL".
order_numberNoDrill into one order/group (from a group row).
trade_numberNoCursor: trade_number of last (next page) or first (previous page) row.
watchlist_idNoRestrict to a watchlist (mutually exclusive with symbols).
investor_typeNoRepeated key. Buyer F/D + seller F/D chips. UI omits it while market is live today.
price_range_toNoMax trade price. Unit: IDR.
time_range_endNoTime window end (literal dotted key). Unit: HH:mm.
broker_operatorNoOR = broker on either side; AND = buyer AND seller as given. Default "FILTER_BROKER_OPERATOR_OR".
price_change_toNoMax % change vs previous close (desktop only; unit inferred). Unit: %.
cursor_directionNoUsed with trade_number for infinite scroll.
price_range_fromNoMin trade price. Unit: IDR.
time_range_startNoTime window start (literal dotted key). Unit: HH:mm.
price_change_fromNoMin % change vs previous close (desktop only; unit inferred). Unit: %.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations it discloses real behavioral quirks: broker codes come back blank live (is_show_bs false), filters get silently ignored during the session, NOT_FOUND means an empty page, and it documents the full return payload including units and the [D]/[F] code suffix. That is exactly the context an agent cannot get from structured fields.

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

Conciseness5/5

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

Front-loaded with the one-line purpose, then caveats, then the return shape — a sensible order for a 25-parameter tool. The long return block is justified because there is no output schema; the only minor duplication is restating is_show_bs false twice.

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 25-param optional-everything tool with no output schema, the description covers the return payload, error semantics, live-market caveats and pagination, which is nearly everything needed to call it correctly. Remaining gaps are minor enumeration details already in the schema.

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?

With 100% schema coverage a 3 is the floor, and the description earns more by adding units the schema lacks: volumes are in lots of 100 shares and values are IDR, and it explains the trade_number/cursor_direction paging contract. It does not cover the enum families or the watchlist_id vs symbols exclusivity beyond restating them.

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?

States a specific resource and verb — "every matched trade, newest first, for one or more symbols or the whole market" — plus the scope of the tape. It is clearly not an aggregate or a book view, but it never names the sibling it differs from (e.g. flow_running_trade_group), so differentiation must be inferred from the returned fields.

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?

Gives concrete when-it-works conditions: broker/investor filters are ignored while the market is open and only apply after close or on a past date, and a past date is valid for a single symbol only. It also names paging via trade_number plus cursor_direction. It stops short of pointing to an alternative tool when the filters are unavailable.

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

Deploy Server

Other Tools