Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Broker activity (what a broker traded)

broker_activity
Read-onlyIdempotent

Retrieve a broker's buy and sell stock rankings over a selected period, using net or gross values and board filters, to follow its market activity.

Instructions

For one broker code: the stocks it bought and sold most over a period, net or gross. Use it to follow a broker across the market.

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

Returns (Stockbit's data field): data{from, to, broker_activity_transaction{brokers_buy[{stock_code, value, lot, avg_price}], brokers_sell[{stock_code, value(negative), lot(negative), avg_price}]}}. value IDR, lot lots (inferred).

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

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_code": "<broker_code>"
    },
    "name": "broker_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoCustom range end; send instead of `period`.
fromNoCustom range start; send instead of `period`.
pageNoNext page while a side returned 50 rows. Default 1.
limitNolimit Default 50.
periodNoRT_PERIOD_* (UI preset 'today' -> RT_PERIOD_LAST_1_DAY). Default "RT_PERIOD_LAST_1_DAY".
broker_codeYesRepeated key (indexes:null). UI max 10 brokers.
market_boardNoMARKET_TYPE_* (UI maps BOARD_TYPE_REGULAR->MARKET_TYPE_REGULER etc.). 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.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: units (lots of 100 shares), currency (IDR), and negative values for sell-side rows. However, it omits other operational traits such as pagination limits and the 50-row-per-side paging behavior that matters when reading results.

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?

Front-loaded with purpose, then units, then return shape, then endpoint — a sensible order. Slight waste in the odd 'lot, blot, slot' phrasing and a fairly verbose inline return block, but nothing is filler 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?

With nine parameters, four enums and no output schema, the definition does the right work: it documents the response field names and sign conventions, plus units and currency. The remaining gaps — multi-broker arrays, paging semantics, and differentiation from sibling broker tools — keep it short of full completeness.

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 baseline is 3, but the description adds real semantics on top: lot/value units, IDR denomination, and the meaning of MARKET_TYPE_* for market_board. One mismatch exists: the description says 'For one broker code' while the schema accepts an array of up to 10 codes, which could mislead an agent about multi-broker support.

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: what one broker bought and sold most over a period, net or gross. It clearly reads as a per-broker ranked flow tool, but it never names or contrasts the adjacent siblings (broker_activity_chart, broker_activity_history, broker_flow), so the agent must infer the boundary.

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?

'Use it to follow a broker across the market' hints at a use case but gives no when-not conditions and no alternative tools for time series or chart views. The agent must infer from sibling names alone which tool to pick.

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