Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Foreign flow summary

foreign_flow_summary
Read-onlyIdempotent

Summarizes net foreign versus domestic buy/sell value or volume for one or more symbols over a chosen period, including mid-day snapshot flags.

Instructions

Foreign vs domestic summary for one or more symbols over a period: net foreign value/volume.

Values IDR. Mid-day snapshots carry is_mid_day / is_break_time.

Returns (Stockbit's data field): data{market_type, from, to, is_mid_day, is_break_time, gross{buy,sell}{raw,formatted}, net{all,regular,others}{raw,formatted}, percentage_foreign_value{raw,formatted}, percentage_domestic_value{raw,formatted}}. ALL-market view disabled while is_mid_day.

Endpoint: GET exodus /order-trade/foreign-domestic/summary.

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_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoto
fromNoOnly when period=TB_PERIOD_UNSPECIFIED.
periodNoperiod Default "TB_PERIOD_LAST_1_DAY".
symbolsYesRepeated key.
data_typeNodata_type Default "DATA_TYPE_VALUE".
market_typeNoFirst load sends UNSPECIFIED; server echoes chosen market_type. Default "MARKET_TYPE_UNSPECIFIED".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 real value beyond that: values are in IDR, mid-day snapshots carry is_mid_day/is_break_time, and the ALL-market view is disabled during mid-day. It does not cover rate limits, per-symbol result ordering, or error behavior.

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 the core purpose, then the return shape, then the endpoint. The long inline field enumeration is dense but justified because no output schema exists; the endpoint line is compact and useful. Minor redundancy between the opening line and the returns block.

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 enumerating the returned data fields, and it flags the IDR unit and the mid-day ALL-market restriction. It is nearly complete for a read-only summary tool; only multi-symbol result structure and pagination/limits are unaddressed.

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 schema already explains from's dependence on period and market_type's UNSPECIFIED-then-echo behavior. The description adds only the IDR unit and the mid-day restriction on the ALL market view, which is marginal extra meaning over the schema.

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: 'Foreign vs domestic summary for one or more symbols over a period: net foreign value/volume.' An agent can tell this is a per-symbol foreign/domestic flow aggregate, though it never explicitly contrasts itself with siblings like foreign_flow or foreign_flow_history.

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 named alternative among the many flow-related siblings. The only conditional guidance is a behavioral caveat ('ALL-market view disabled while is_mid_day'), which is a constraint rather than a selection 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