Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Trade book (done summary)

flow_trade_book
Read-onlyIdempotent

Retrieve Stockbit trade-book data grouped by price or time to compare buy and sell lots, frequency, and value for a symbol across a date range.

Instructions

How much traded at each price (group_by GROUP_BY_PRICE) or in each time bucket (GROUP_BY_TIME), split into buy and sell side: frequency, lots and value. The "done summary" view.

Volumes (lot, blot, slot) are in lots of 100 shares; values are IDR. Numbers come pre-formatted as strings (e.g. "1,372,029", "134.55B").

Returns (Stockbit's data field): data{date, from, to, previous_price, is_show_pre_post, is_fca_stock, market_hour_steps[], book[{price '1,095', time, buy{lot,frequency,percentage,value,value_percentage}, sell{...}, pre_open{...}, post_close{...}, total{...}}], book_total{buy_lot, sell_lot, buy_frequency, sell_frequency, buy_value, sell_value, percentage, big_money, overall_net_per_min_percentage{buy,sell,buy_value,sell_value}, big_money_net_per_min_percentage}}. All numbers are PRE-FORMATTED strings ('1,372,029', '134.55B', '-'); lot unit = lots.

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

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

Input Schema

NameRequiredDescriptionDefault
toNoCustom range end; send instead of `period`.
dateNoSingle day (UI default = today).
fromNoCustom range start; send instead of `period`.
modeNoBIG_MONEY gated by feature flag all-b-bigmoney-tradeflow-eligibility. Default "TRADE_BOOK_MODE_OVERALL".
periodNoPreset alternative to date/from/to.
symbolYesTicker.
sort_byNoOnly with GROUP_BY_TIME. Default "SORT_BY_TIME".
group_byNoPrice ladder vs time buckets. Default "GROUP_BY_PRICE".
time_intervalNoOnly with GROUP_BY_TIME (hard-coded '10m'). Default "10m".
sort_directionNoSeen in web HAR with GROUP_BY_TIME (ASC).

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 declare the safe read-only and idempotent behavior, but the description adds important context about pre-formatted numeric strings, lot units, IDR values, and the returned data structure. It does not cover auth or rate-limit behavior, but the added return-shape and formatting details are substantial.

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?

The description is front-loaded with purpose and usage, then moves into units, return fields, and endpoint. It is mostly well-structured, though the pre-formatted-string caveat is repeated and the returns block is dense.

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?

Given ten parameters and no output schema, the description is fairly complete: it explains the core output shape, units, formatting quirks, and endpoint. The input schema carries parameter details, though the description could say more about date/period interaction and mode selection.

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 the schema already documents all ten parameters, including enums and date/period alternatives. The description reinforces group_by semantics and output units, but it adds little parameter guidance beyond what the schema provides.

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 description clearly states what the tool returns: traded volume at each price or time bucket, split by buy/sell side with frequency, lots, and value. It also labels this as the "done summary" view, which helps distinguish it, but it does not explicitly contrast it with sibling tools such as running trade views.

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 implied through the group_by modes and the "done summary" framing, giving an agent enough to infer when to request price-level versus time-bucket data. However, it does not explicitly state when to use this tool instead of alternatives or any exclusions.

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