Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Broker summary (new endpoint)

broker_summary_v2
Read-onlyIdempotent

Fetches broker buy and sell activity for a stock symbol across a chosen period, with net or gross values filtered by market board and investor type.

Instructions

The newer broker summary the desktop Broker Position module uses: buyers and sellers of one symbol over a period with net or gross values.

Volumes (lot, blot, slot) are in lots of 100 shares; values are IDR. Note market_board takes MARKET_TYPE_* values here.

Returns (Stockbit's data field): data{from, to, price_activity{close_price}, broker_summary_transaction{brokers_buy[{broker_code, type, net_value, net_lot, avg_price}], brokers_sell[...]}}.

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

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

Input Schema

NameRequiredDescriptionDefault
toNoto
fromNoUI also sends from=today,to=today-3d alongside period (ignored?).
limitNolimit Default 100.
periodNoperiod Default "BROKER_SUMMARY_PERIOD_LATEST".
symbolYesTicker.
market_boardNoMARKET_TYPE_* family. Default "MARKET_TYPE_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 establish readOnly/idempotent/non-destructive/openWorld, so the description's job is to add context — and it does: it discloses the unit conventions (lot/blot/slot in lots of 100 shares, values in IDR), the underlying endpoint, and the exact response envelope. It does not mention rate limits or pagination behavior beyond the limit default.

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 what the tool is, then units, then the return shape, then the endpoint — a sensible layered order. The inline return-shape dump is dense but earns its place because no output schema exists; the endpoint line is marginal but harmless.

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 8 parameters, four enums, and no output schema, the description covers the two things an agent most needs: unit conventions and the shape of the response. Remaining gaps are the ambiguous period-vs-from/to interaction and limit/pagination behavior, which are useful but secondary.

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 coverage is 100%, so the baseline is 3, and the description mostly matches rather than exceeds it. It adds value by explaining the units of the returned values and by clarifying that transaction_type means net vs gross, but period semantics and the from/to-versus-period interaction (which the schema itself flags with a '?') are left unexplained.

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 uses a specific verb and resource: buyers/sellers for one symbol over a period, with net or gross values, and identifies it as the newer endpoint backing the desktop Broker Position module. That clearly distinguishes it in kind from portfolio/flow siblings, though it never explicitly contrasts with the 'broker_summary' sibling whose name it echoes.

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 when-to-use or when-not-to-use guidance, and in particular nothing telling the agent whether to prefer this over the plain 'broker_summary' sibling or when one of the other broker_* tools is more appropriate. The only hint is the incidental remark that the desktop Broker Position module uses 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