Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Broker activity chart

broker_activity_chart
Read-onlyIdempotent

Retrieve time-series charts of chosen brokers' cumulative net buying and selling, optionally filtered by stock symbols, date range, market board, and investor type.

Instructions

Time series of chosen brokers' net activity, optionally within chosen symbols.

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

Returns (Stockbit's data field): data{from, to, chart_data[{type TYPE_CHART_VALUE|TYPE_CHART_VOLUME, symbols[], charts[{symbol, chart[{date, time, value{raw,formatted}}]}]}]} — cumulative net per stock for the broker(s).

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

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": {
      "brokers_code": "<brokers_code>"
    },
    "name": "broker_activity_chart"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoCustom range end; send instead of `period`.
fromNoCustom range start; send instead of `period`.
periodNoperiod Default "RT_PERIOD_LAST_1_DAY".
symbolsNoOptional stock subset; server returns default symbols otherwise (INVALID_PARAMETER if bad).
brokers_codeYesNOTE plural 'brokers_code'; repeated key.
market_boardNoBOARD_TYPE_* family. Default "BOARD_TYPE_REGULAR".
investor_typeNoinvestor_type Default "INVESTOR_TYPE_ALL".

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 readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety is covered and the description adds real context on top: units (lots of 100 shares, values in IDR), the cumulative-net semantics per stock, the underlying endpoint, and the fact that unspecified symbols fall back to server defaults. It stops short of stating any limits on range size or how large a chart payload can grow.

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?

Purpose and units are front-loaded, then the return shape, then the endpoint. The nested return-type string is dense and symbol-heavy, but with no output schema it earns its place as the only description of what comes back; nothing is redundant filler.

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?

Seven parameters, three of them enums, and no output schema — the description compensates by spelling out the response envelope, the two chart value types, and the cumulative-net meaning, plus the units. What is missing is range-size behaviour and whether symbol/broker selections interact, but an agent can call this correctly from what is given.

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 every parameter is already documented, including the plural brokers_code note, the period/from-to exclusivity, and the enum families. The description only reinforces 'chosen brokers' and 'chosen symbols' and adds the unit convention, which informs interpretation of output rather than of inputs; the 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?

The opening sentence gives a specific resource and shape: a time series of chosen brokers' net activity, optionally scoped to symbols. It is clear what the tool returns, but it does not differentiate itself from near-neighbours such as broker_activity, broker_activity_history, or broker_flow, leaving the agent to guess why it would pick a chart over a summary.

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 sibling is named as an alternative. The only usage-adjacent text ('optionally within chosen symbols', 'send instead of period') is parameter mechanics that duplicate the schema rather than helping the agent choose this tool over broker_activity or broker_activity_history.

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