Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Running trade grouped by order

flow_running_trade_group
Read-onlyIdempotent

Retrieve grouped running trades for one symbol, aggregating partial fills of each order with price, lot, value, buyer, seller, and filters for date, broker, board, and action.

Instructions

Running trade with the partial fills of one order grouped together, for one symbol.

Volumes (lot, blot, slot) are in lots of 100 shares; values are IDR.

Returns (Stockbit's data field): data{date, ..., running_trade_group[{id, time, code, price{formatted}, change{raw,formatted}, action, group_action (RUNNING_TRADE_ACTION_TYPE_BUY|SELL), lot{raw,formatted}, value{raw,formatted}, buyer[{code,abbreviation}], seller[{code,abbreviation}], order_number, market_board, trade_number}]} (from mapGroupItemToRowData; no HAR).

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

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": {
      "symbols": "<symbols>"
    },
    "name": "flow_running_trade_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoHistory date; UI only sends for a single symbol and not today ('Running Trade History Only Available for a Single Stock').
sortNoConverted with toGroupSort() to uppercase when no symbol. Default "DESC".
limitNoPage size (store default). Default 50.
cursorNoPagination: id of the last running_trade_group row.
symbolsYesExactly one ticker ([symbol]); UI sends symbols=[''] when none selected.
order_byNoorder_by 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.
market_boardNoBoard filter (BOARD_TYPE_* family). Default "BOARD_TYPE_ALL".
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: %.
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

A3.5/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), lowering the bar. The description adds genuinely useful context beyond them: volume units in lots of 100 shares, IDR denominations, the history/single-symbol restriction referenced via the date parameter, and the concrete endpoint. However it leaves operational behavior opaque: no pagination semantics for cursor/limit, no default ordering behavior, and no note on how grouping interacts with paging.

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?

Purpose and unit conventions are correctly front-loaded, which is the right structure for a high-parameter tool. The return-value sentence then degenerates into a raw field dump including implementation notes such as '(from mapGroupItemToRowData; no HAR)' and every nested '{raw,formatted}' wrapper, which is verbose relative to what an agent needs and could be summarized as the meaningful fields.

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?

With 21 parameters, 5 enums and no output schema, the description does the heavy lifting reasonably well: it discloses return shape, unit conventions, the endpoint, and the single-symbol history restriction. Gaps remain around pagination (cursor/limit interplay) and sorting defaults, which matter for a tool returning grouped rows.

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 description coverage is 100% across 21 parameters with enums documented, so the schema carries most of the load and the baseline of 3 applies. The description adds value by stating the shared unit convention for all numeric filters (lots of 100 shares, values in IDR) and by surfacing the single-symbol constraint on historical dates, which is a cross-parameter rule rather than per-field text.

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?

The opening sentence names a specific resource (running trade), the distinctive transformation (partial fills of one order grouped together), and the scope (one symbol), which is enough to separate it functionally from the ungrouped sibling flow_running_trade. It stops short of naming that sibling or any other alternative, so the differentiator must be inferred from wording rather than stated as routing.

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?

Usage is only implied: 'grouped together, for one symbol' signals this is the per-order aggregation view and constrains input to a single ticker. There is no explicit when-to-use vs when-to-use-instead statement, no mention of flow_running_trade or flow_trade_book as alternatives, and no guidance on when order-level aggregation is preferable.

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