Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Top stocks by investor flow

market_top_stocks
Read-onlyIdempotent

Rank stocks by net, gross, or buy/sell value for foreign, domestic, or all investors over a chosen period and market type, with IDR totals, buy/sell summaries, and mid-day snapshots.

Instructions

Stocks ranked by net (or buy/sell) value of an investor type (all, foreign, domestic) over a period.

Values IDR. Mid-day snapshots carry is_mid_day.

Returns (Stockbit's data field): data{response_info{page, start_date, end_date, investor_type, market_type, value_type, max_day_duration}, display_option{enabled_value_type{net,gross}, is_mid_day, is_break_time, foreign_value_column}, summary{buy,sell,net}{raw,formatted}, banner_message, + buy/sell/total stock rows (row field names not resolved statically)}.

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

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

Input Schema

NameRequiredDescriptionDefault
endNoend Default "".
pageNoNext = response_info.page+1. Default 1.
startNoCustom range (sent '' when period set). Range capped by response_info.max_day_duration. Default "".
periodNoperiod Default "TOP_STOCK_PERIOD_LATEST".
value_typeNovalue_type Default "VALUE_TYPE_NET".
market_typeNomarket_type Default "MARKET_TYPE_REGULER".
investor_typeNoDesktop first call sends *_UNSPECIFIED to get server defaults. 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 cover read-only, idempotent, non-destructive and open-world, and the description adds genuinely useful context beyond them: currency units (IDR), the mid-day snapshot caveat, the max_day_duration range cap, and the endpoint shape. It also honestly flags that stock row field names are not statically resolved, which is important for the calling agent; only auth and rate-limit behavior are absent.

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 the first sentence, followed by units and caveats, then the return shape. The return-field enumeration is long but earns its place because there is no output schema; the endpoint path at the end is the least valuable line.

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 seven optional parameters, no output schema and a nested-looking response, the description does the necessary work by describing response_info, display_option, summary and row contents. It is nearly complete; a sentence on choosing period over start/end and on sensible defaults for a first call would close the gap.

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 schema already documents every parameter, including the page+1 pagination rule and the period-vs-start/end precedence. The description adds little parameter-level meaning beyond repeating the investor-type and net/buy/sell dimensions and the IDR unit, so the baseline of 3 applies.

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-like operation (ranking) on a specific resource (stocks) with the ranking dimension spelled out: net or buy/sell value by investor type over a period. The subject matter is distinguishable from broker-oriented siblings, but no sibling is named, so the agent must infer the boundary itself.

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. The only ambient hints are behavioral notes about IDR values and mid-day snapshots; which tool to pick when compared to broker_top or foreign_flow is left entirely to inference.

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