Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Trade flow chart

flow_trade_flow
Read-onlyIdempotent

Retrieve intraday buy-versus-sell trade flow for a stock, including cumulative value, volume, and frequency per interval, with date or range filters and optional pre/post-market exclusion.

Instructions

Trade flow over the day: cumulative buy vs sell value, volume and frequency per interval for one symbol, the series behind Stockbit's Trade Flow chart.

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

Returns (Stockbit's data field): data{date, from, to, is_show_pre_post, is_fca_stock, first_available_date, buy[], sell[], big_money_buy[], big_money_sell[], prices[], net_values[], net_values_volume[], big_money_net_values[], big_money_net_values_volume[] — each point {time 'HH:mm', date, lot{raw,formatted}, value{raw,formatted}, frequency{raw,formatted}} (raw strings; lot=lots, value=IDR); pre_post, big_money_pre_post, book_total{... same as trade-book ...}, historical_raw/intraday_raw{buy_lot_raw, sell_lot_raw, buy_value_raw, sell_value_raw}}. Multi-day ranges return DAILY buckets; UI then refetches date= for the live day and merges.

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

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

Input Schema

NameRequiredDescriptionDefault
toNoCustom range end; send instead of `period`.
dateNoSingle day.
fromNoCustom range start; send instead of `period`.
periodNoPreset alternative.
symbolYesTicker.
data_modeNoRepeated key; exclude pre-opening / post-closing. Default [].
time_intervalNoUI hard-codes '1m'. (User backend used '5m'; not seen in UI/HAR.) Default "1m".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior5/5

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

Annotations already declare a safe, idempotent, read-only open-world call, and the description goes well beyond them: it pins units (lots of 100 shares for lot/blot/slot, IDR for values), documents the full response shape, and discloses the non-obvious multi-day behavior where ranges return DAILY buckets and the UI refetches date=<to> to merge the live day.

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 in the first sentence, followed by units and then the return contract. The compressed field-list notation (data{...}, {raw,formatted}) is dense but earns its space given the absence of an output schema.

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 7-parameter read tool with no output schema, the description carries the needed weight by enumerating return fields and units. Minor gaps remain: no default date behavior when neither date nor period is supplied, and no failure or empty-interval behavior.

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 baseline is 3, but the description adds real meaning: the date/<to> refetch interplay for live-day merging, the unit conventions that govern the numbers parameters select, and the endpoint path. It still does not explain defaults or precedence for period vs from/to beyond what the schema says.

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 verb and resource: cumulative buy vs sell value, volume and frequency per interval for one symbol, framed as the series behind Stockbit's Trade Flow chart. It does not explicitly contrast itself with the closely named siblings flow_trade_book or flow_running_trade, so an agent must infer the split from the field lists.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative among the many flow_* siblings. Usage is only implied by the description of the returned series and the note about multi-day ranges.

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