Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Broker distribution

broker_distribution
Read-onlyIdempotent

Retrieve top broker buy and sell distribution for a stock, showing counterparties and value or volume by price across a chosen period and market board.

Instructions

Which brokers bought and sold one symbol at which prices: broker x price matrix of value or volume (data_type), the Broker Distribution view.

Volume amounts are gross lots; values IDR. market_board takes MARKET_TYPE_* values. On the web Stockbit shows this only to accounts with equity above Rp10.000.000; the server may enforce it.

Returns (Stockbit's data field): data{date_info, start_date, end_date, by_value{top_broker_buy[{detail{code,type 'Lokal'|'Asing'|'Pemerintah',amount}, distribute_to[{code,type,amount}]}], top_broker_sell[...]}, by_volume{same}} — top 12 brokers each side and their counterparties. amount = gross IDR (VALUE) or gross LOTS (VOLUME: XL 1,444,828 lots x100 x avg 968 = 139.87B IDR). Web UI paywall text: 'Fitur ini hanya tersedia untuk Nasabah dengan Equity di atas Rp10.000.000' (desktop fetches regardless).

Endpoint: GET exodus /order-trade/broker/distribution.

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

Input Schema

NameRequiredDescriptionDefault
toNoCustom range end; send instead of `period`.
dateNoAlways sent empty by UI. Default "".
fromNoCustom range start; send instead of `period`.
periodNoPreset; omit when from/to given. Default "TB_PERIOD_LAST_1_DAY".
symbolYesTicker.
data_typeNoOnly the matching by_value/by_volume block is filled. Default "BROKER_DISTRIBUTION_DATA_TYPE_VALUE".
market_boardNoNOTE: MARKET_TYPE_* values under the key market_board. Default "MARKET_TYPE_REGULER".
investor_typeNoinvestor_type Default "INVESTOR_TYPE_ALL".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare a safe read operation, and the description adds real behavioral context on top: the equity > Rp10.000.000 access restriction and that the server may enforce it, the units for each data_type (gross lots vs IDR), and the top-12-per-side scope. It even notes the desktop UI fetches regardless of the displayed paywall message.

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 opening sentence front-loads the purpose and units, and every subsequent block carries information. The return-shape paragraph is a dense run-on that is harder to parse than a structured list, but it is justified because no output schema exists.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With eight parameters, no output schema, and a gated endpoint, this tool needs the return structure, units, and access constraints spelled out — and the description supplies all three, plus the underlying endpoint. An agent has what it needs to call this correctly and interpret the response.

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 the schema already documents every parameter and the baseline is 3. The description still adds semantic value by explaining that data_type populates only the matching block, and by spelling out that market_board carries MARKET_TYPE_* values — details that clarify enum intent beyond the raw field descriptions.

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 opens with a specific statement of what the tool returns: a broker x price matrix of value or volume for one symbol, tied to the 'Broker Distribution view'. That is a concrete verb+resource, but it never names the neighboring concepts (broker_flow, broker_summary, broker_top) to say how this differs from them.

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: it's a per-symbol broker breakdown, with data_type selecting the value or volume view. There is no explicit when-to-use or when-not-to-use guidance versus alternatives, though the paywall note gives useful preconditions for calling it.

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