Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Broker summary (bandarmology)

broker_summary
Read-onlyIdempotent

Retrieve top buyer and seller brokers for a stock symbol over a chosen period, including net lots, value, average price, and accumulation/distribution signals.

Instructions

Top buyer and seller brokers of one symbol over a period, with net lots, value and average price, plus the accumulation/distribution read (bandar detector). The classic broker summary.

blot/slot are net lots; blotv is gross shares and bvalv gross IDR, so bvalv/blotv is the average price. Broker data is end-of-day or mid-day, not tick-live.

Returns (Stockbit's data field): data{from, to, bandar_detector{average, value, volume(lots), total_buyer, total_seller, number_broker_buysell, broker_accdist, top1/top3/top5/top10/avg/avg5{accdist 'Big Dist'|'Normal Dist'|..., amount IDR, percent, vol}}, broker_summary{symbol, brokers_buy[{netbs_broker_code, netbs_stock_code, netbs_date 'YYYYMMDD', blot (net lots), bval (net IDR), blotv (gross buy volume, SHARES), bvalv (gross buy IDR; bvalv/blotv = netbs_buy_avg_price), netbs_buy_avg_price, freq, type 'Lokal'|'Asing'|'Pemerintah'}], brokers_sell[{... slot, sval (negative), slotv, svalv, netbs_sell_avg_price}]}}. All numerics are strings (some in exponent form).

Endpoint: GET exodus /marketdetectors/{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_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoCustom range end; send instead of `period`.
fromNoCustom range start; send instead of `period`.
limitNolimit Default 25.
periodNoOmit when from/to given. Default "BROKER_SUMMARY_PERIOD_LATEST".
symbolYessymbol
market_boardNoMARKET_BOARD_* family. Default "MARKET_BOARD_REGULER".
investor_typeNoinvestor_type Default "INVESTOR_TYPE_ALL".
transaction_typeNotransaction_type Default "TRANSACTION_TYPE_NET".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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, open-world), and the description adds genuinely new behavioral context: the data is EOD/mid-day rather than tick-live, all numerics come back as strings sometimes in exponent form, and sell-side values like sval are negative. That said, it says nothing about rate limits, permissions, or what happens with large limit values.

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 purpose is front-loaded in the first sentence, followed by field semantics, freshness, and the return shape. The nested-brace return dump is dense but earns its place because no output schema exists; it could still be tightened into a flatter list.

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 eight parameters, no output schema, and a complex nested payload, the description does the heavy lifting by enumerating the returned data structure, field meanings, and data-freshness constraints. The main gap is the absence of any differentiation from broker_summary_v2, which an agent would need to choose correctly.

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 every parameter including the period/from-to interplay and enum families, making 3 the baseline. The description reinforces 'one symbol over a period' but does not clarify limit/pagination behavior or the practical meaning of market_board and investor_type choices.

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 first sentence names a specific verb and resource: top buyer/seller brokers for one symbol over a period, including net lots, value, average price and a bandar/accumulation-distribution read. It is clearly distinguishable from generic flow tools, but 'The classic broker summary' only gestures at the sibling broker_summary_v2 without saying how the two differ.

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 routing to alternatives such as broker_summary_v2 or broker_activity despite those siblings existing. The only contextual note is a freshness caveat ('end-of-day or mid-day, not tick-live'), which describes data timing rather than selection criteria.

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