Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Foreign vs domestic flow

foreign_flow
Read-onlyIdempotent

Retrieves foreign and domestic buy, sell, net, and totals for a stock symbol over a selected period or custom date range, providing chart-series data for Foreign Flow analysis.

Instructions

Foreign and domestic buy, sell and net for one symbol over a period range, as a chart series with totals (the Foreign Flow tab).

volume fields are shares; values IDR. market_type takes MARKET_TYPE_REGULAR or MARKET_TYPE_ALL_MARKET.

Returns (Stockbit's data field): data{from, to, last_updated, summary{date_range, foreign_buy, foreign_sell, net_foreign, domestic_buy, domestic_sell, net_domestic {label, value{raw,formatted}}, all_markets_summary[], volume{...}}, value{label 'Value (IDR)', total, foreign_buy/sell, domestic_buy/sell, foreign_total, domestic_total {value, percentage}}, volume{same, SHARES}, frequency{same}}.

Endpoint: GET exodus /findata-view/foreign-domestic/v1/chart-data/{symbol}.

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": "foreign_flow"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoCustom range end; send instead of `period`.
fromNoCustom range start; send instead of `period`.
periodNoOmit when from/to given (custom range; min date 2025-01-01, max 6 months). Default "PERIOD_RANGE_1D".
symbolYessymbol
market_typeNoNOTE different spelling from MARKET_TYPE_REGULER. Default "MARKET_TYPE_REGULAR".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false already supplied, the description still adds meaningful context: the data source is Stockbit's data field, units are shares for volume and IDR for values, and the underlying endpoint is disclosed. It does not mention latency/granularity of the chart series or rate limits, which keeps it 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?

The purpose is front-loaded in a single strong sentence, and the endpoint line is compact. The long parenthetical dump of the return structure is dense but earns its place because no output schema exists, though it could have been formatted more readably.

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

Completeness5/5

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

For a five-parameter read-only tool with no output schema, the description covers units, the source data shape, enum quirks, and the raw endpoint. An agent can call it correctly without further guessing, and the only omission (series granularity) is minor.

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%, so the baseline is 3. The description reinforces the market_type enum values and warns about the MARKET_TYPE_REGULER vs MARKET_TYPE_ALL_MARKET spelling, but it adds no meaning beyond the schema for symbol, period, from or to.

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 opens with a specific verb-and-resource statement: foreign and domestic buy/sell/net for one symbol over a period range, returned as a chart series with totals, and ties it to the 'Foreign Flow tab'. It is clearly distinguishable from a generic flow tool, but it never names or contrasts the siblings foreign_flow_history and foreign_flow_summary, which an agent must still disambiguate on its own.

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 phrase 'for one symbol over a period range' plus the note that from/to replace period. There is no explicit statement of when this chart-series tool is preferred over the history or summary siblings, and no prerequisites or exclusions are given beyond the parameter substitution rule.

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