Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Broker flow chart

broker_flow
Read-onlyIdempotent

Retrieve the cumulative net buy/sell flow of top brokers for a stock symbol over a selected period, with optional broker code filtering.

Instructions

Broker flow: the cumulative net buy/sell of the top brokers in one symbol over time (the Broker Flow chart). Filter to a broker with broker_code.

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

Returns (Stockbit's data field): data{from, to, data_last_updated, date_session_info, price_chart_data[{date, time 'HH:mm', datetime_label, value{raw}, open{raw}, high{raw}, low{raw}}], broker_chart_data[{type TYPE_CHART_VALUE|TYPE_CHART_VOLUME, brokers[codes], charts[{broker_code, chart[{date,time,value{raw,formatted}}]}]}]}. Values are cumulative net per broker: VALUE in IDR, VOLUME in lots (XL 517,461 = marketdetectors blot). 1-min points for 1D, hourly for 7D, daily beyond.

Endpoint: GET exodus /order-trade/running-trade/chart/{symbol}.

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_flow"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoCustom range end; send instead of `period`.
fromNoCustom range start; send instead of `period`.
periodNoPreset ('Latest'). Mutually exclusive with from/to. Default "RT_PERIOD_LAST_1_DAY".
symbolYessymbol
broker_codeNoRepeated key (indexes:null). Omit to let server pick top-5 brokers (response.brokers).
market_boardNoBOARD_TYPE_* family; default REGULAR, CASH for rights tickers (symbol contains '-R'). Default "BOARD_TYPE_REGULAR".
investor_typeNoinvestor_type Default "INVESTOR_TYPE_ALL".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds genuine context on top: values are cumulative net per broker, VOLUME is in lots of 100 shares while VALUE is in IDR, and temporal resolution varies by period (1-min for 1D, hourly for 7D, daily beyond). It does not mention rate limits or data freshness beyond the data_last_updated field name.

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?

Purpose is front-loaded, units and resolution follow, and the dense return-shape block comes last. The data{} field tree is long and syntactically heavy, but it earns its place because no output schema exists; minor tightening of the type/broker/charts nesting could improve readability.

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 no output schema, the description correctly compensates by sketching the exact response envelope (price_chart_data and broker_chart_data, raw/formatted values) plus unit and granularity caveats. For a 7-parameter read-only chart tool with full schema coverage, almost everything an agent needs to call and interpret it is present.

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?

Schema description coverage is 100%, so every parameter including the from/to mutual exclusion with period and the market_board default rule is already documented in structured data. The description only restates the broker_code filtering behavior and adds unit semantics, which is the expected baseline-3 contribution when the schema does the heavy lifting.

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 gives a specific verb and resource — "cumulative net buy/sell of the top brokers in one symbol over time (the Broker Flow chart)" — and names the endpoint (GET /order-trade/running-trade/chart/{symbol}). It does not explicitly distinguish itself from close siblings like broker_activity_chart or broker_distribution, so it stops short of a 5.

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?

It states one concrete usage rule — "Filter to a broker with broker_code" — and the schema supplies the top-5 default when omitted. Beyond that there is no guidance on when to pick this chart over broker_activity_chart or the flow_* siblings, so the when-to-use rationale is only implied.

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