Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Foreign flow history

foreign_flow_history
Read-onlyIdempotent

Retrieve daily foreign versus domestic net flows and historical prices for one or more stock symbols over a chosen period, with values in IDR, to analyze foreign investor activity.

Instructions

Daily foreign vs domestic net for one or more symbols over a period.

Values IDR.

Returns (Stockbit's data field): data{from, to, historical_net[{date, datetime_label, datetime_label_table, net_foreign{raw,formatted}, foreign_buy, foreign_sell, average_price, percentage_foreign_value, percentage_domestic_value, net_lot, net_frequency}], historical_price[{date, open, high, low, close{raw,formatted}}]}.

Endpoint: GET exodus /order-trade/foreign-domestic/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": {
      "symbols": "<symbols>"
    },
    "name": "foreign_flow_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoto Default "".
fromNoOnly when period=TB_PERIOD_UNSPECIFIED (else sent as ''). Default "".
periodNoTB_PERIOD_UNSPECIFIED => use from/to. Default "TB_PERIOD_LAST_7_DAYS".
symbolsYesRepeated key.
market_typeNomarket_type Default "MARKET_TYPE_REGULER".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 fully covered elsewhere. The description does add genuinely new context – the IDR currency unit and the exact response payload shape – but says nothing about rate limits, auth, 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.

Conciseness4/5

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

Purpose and units are front-loaded in two short lines before the payload detail, which is a sensible ordering. The long return-field enumeration is dense but earns its place because there is no output schema to carry that information.

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 compensates by fully enumerating the nested return fields (historical_net, historical_price), which is the main completeness risk for this tool. The remaining gap is the absence of any routing hint versus the similarly named flow siblings.

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 description coverage is 100%, so the enum values for period and market_type and the date pattern for from/to are already documented. The description reinforces the symbol-scoping and 'over a period' semantics, but adds little on top of the schema; baseline-plus is appropriate given the schema does the heavy lifting.

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 concrete verb+resource statement: 'Daily foreign vs domestic net for one or more symbols over a period,' which tells an agent exactly what data comes back. It stops short of differentiating itself from the sibling flow tools (foreign_flow, foreign_flow_summary), so an agent still has to guess which of the three to use.

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 when-to-use guidance at all – no statement of when this tool is preferred over foreign_flow or foreign_flow_summary, and no note about cost or prerequisites. The only usage-adjacent hint is the raw endpoint line, which doesn't help an agent choose between tools.

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