Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Broker activity history

broker_activity_history
Read-onlyIdempotent

Track day-by-day net buy/sell activity of chosen brokers in selected symbols to spot steady accumulation or distribution.

Instructions

Day-by-day (or weekly/monthly) net activity of chosen brokers in chosen symbols, for spotting steady accumulation or distribution.

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

Returns (Stockbit's data field): data{date_from, date_to, pagination{has_next,...}, records[{date, broker_name?, trade_activity{net_summary{value,lot,avg_price}, buy_summary, sell_summary, foreign_summary{net_foreign,foreign_buy,foreign_sell}, total_buy_lot, total_sell_lot}, price_activity{close_price,...}, return_summary}], summary{data[{date_from, date_to, net_summary}]}}.

Endpoint: GET exodus /order-trade/broker/activity/historical.

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": {
      "broker_codes": "<broker_codes>",
      "symbols": "<symbols>"
    },
    "name": "broker_activity_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodNoTable view default; omit for date_from/date_to. Default "RT_PERIOD_LAST_1_YEAR".
date_toNodate_to
symbolsYesRepeated key.
intervalNointerval Default "INTERVAL_DAILY".
date_fromNoNOTE: date_from/date_to, not from/to.
broker_codesYesRepeated key (custom serializer).
market_boardNoBOARD_TYPE_* family here. Default "BOARD_TYPE_REGULAR".
net_intervalNoCalendar view sends INTERVAL_MONTHLY to get per-month net summary.
investor_typeNoinvestor_type Default "INVESTOR_TYPE_ALL".
pagination_pageNoLiteral dotted key. Default 1.
pagination_limitNoLiteral dotted key. Default 25.
transaction_typeNoIn query key; not set by observed callers.

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 declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds genuinely useful context beyond that: units (lots of 100 shares, values in IDR), the shape of the returned data, and the backing endpoint. It does not disclose rate limits, auth requirements, or data latency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose sentence is front-loaded and earns its place, but the returns section is a raw, densely nested field dump that is hard for an agent to parse, and the trailing 'Endpoint: GET exodus ...' line adds little decision value. Overall it is not bloated, but it is not cleanly structured either.

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

Completeness3/5

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

With 12 parameters, six enums, and no output schema, this is a complex tool, and the description does cover return shape and units. It leaves important gaps: the period-vs-date_from/date_to exclusivity (the schema only hints at it), the calendar-vs-table distinction implied by net_interval, and pagination behaviour.

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%, which sets the baseline at 3 even though several schema descriptions are cryptic ('Repeated key.', 'Literal dotted key.'). The description's unit clarifications (lots of 100 shares, IDR) add meaning beyond the schema, but it does not explain the relationships between period/date_from/date_to, or between interval and net_interval.

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 gives a specific verb+resource+scope: day-by-day (or weekly/monthly) net activity of chosen brokers in chosen symbols. It does not, however, distinguish itself from plausible siblings such as broker_activity, broker_activity_chart, or broker_flow, so an agent must infer which of the broker-activity family to call.

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?

The phrase 'for spotting steady accumulation or distribution' implies the analytical use case, which is real if thin guidance. There is no explicit when-to-use/when-not, no mention of alternatives, and no stated prerequisites for the required broker_codes and symbols.

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