Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Top brokers of the market

broker_top
Read-onlyIdempotent

Ranks brokers market-wide by total, buy, sell, or net value, volume, or frequency over a chosen period so you can compare broker flows and identify accumulation or distribution.

Instructions

Brokers ranked market-wide by total, buy, sell or net value over a period.

total_volume is shares; values IDR. Mid-day snapshots carry is_mid_day.

Returns (Stockbit's data field): data{date{from,to,idx}, is_mid_day, is_break_time, list[{code, name, group BROKER_GROUP_{LOCAL,FOREIGN,GOVERNMENT}, investor_type, total_value, net_value, buy_value, sell_value (IDR strings), total_volume (string, looks like SHARES), total_frequency}]} (112 brokers).

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

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "broker_top"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoCustom range end; send instead of `period`.
fromNoCustom range start; send instead of `period`.
sortNosort Default "TB_SORT_BY_TOTAL_VALUE".
orderNoorder Default "ORDER_BY_DESC".
periodNoperiod Default "TB_PERIOD_LAST_1_DAY".
eod_onlyNotrue for broker pickers/navigator (end-of-day list).
market_typeNoKey is market_type here. Default "MARKET_TYPE_ALL".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds meaningful context beyond that: unit semantics (total_volume in shares, values in IDR strings), the fact that mid-day snapshots carry is_mid_day/is_break_time, the list size (~112 brokers), and the underlying endpoint. It does not discuss pagination or rate limits, so it falls short of a 5.

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-loads the summary sentence, then units, then return shape, then endpoint — a sensible order. The long Returns block is dense but earns its place because no output schema exists; only the trailing 'Endpoint: GET exodus ...' line is marginal internal detail.

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 no output schema, the description correctly compensates by enumerating the returned fields, their types, and the group/investor_type enums. For a 7-parameter, zero-required tool it could still say that all parameters are optional with server defaults and how from/to interact with period, but nothing essential to a correct call is missing.

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% and each parameter (period, from/to, sort, order, eod_only, market_type) is documented there, so the schema carries the burden. The description adds only 'over a period' and the unit notes, which map to output fields rather than inputs; it says nothing about the from/to-versus-period exclusivity or what MARKET_TYPE_REGULER/TUNAI/NEGO mean. Baseline 3 is appropriate.

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+resource+scope: brokers ranked market-wide by total, buy, sell or net value over a period. The 'market-wide' qualifier implicitly separates it from per-stock siblings like broker_activity or broker_distribution, but no sibling is named explicitly.

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 by the 'market-wide' scope and the mention of a period; there is no explicit when-to-use or when-to-prefer-an-alternative statement. The 'eod_only for broker pickers/navigator' note in the schema is the only conditional guidance, and it lives in the schema rather than the description.

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