Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Market movers

market_movers
Read-onlyIdempotent

Retrieve ranked stock lists—top gainers, losers, most active by value, volume, or frequency, and net foreign buy/sell—to identify current market movers.

Instructions

Ranked stock lists: top gainers, losers, most active by value/volume/frequency, net foreign buy/sell, and more (mover_type). Defaults to the main, development, acceleration and new economy boards.

volume.raw is lots; values IDR. Net foreign is stamped per session (net_foreign_updated_at).

Returns (Stockbit's data field): data{mover_type, mover_list[{stock_detail{code,name,icon_url,has_uma,notations,corpaction}, price, change{value,percentage}, value{raw IDR}, volume{raw LOTS}, frequency{raw}, net_foreign_buy{raw}, net_foreign_sell{raw}, net_buy, net_sell, big_money_net_value, buy/sell_value_percentage, big_money_*_value_percentage, bid_percent, iepiev_detail{iep,iev,ieval,iep_change,...}, catalog_detail{...}, market_cap}], is_show_net_foreign, net_foreign_updated_at 'YYYY-MM-DD', net_foreign_session_info{formatted,date,is_last_session}, pagination{page,limit,has_next,has_prev}}. Net foreign is session/day-stamped (not tick-realtime). 50 rows.

Endpoint: GET exodus /order-trade/market-mover.

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

Input Schema

NameRequiredDescriptionDefault
pageNoStock-group views use 1.
limitNoStock-group views use 100.
catalog_idNoGroup detail.
mover_typeNofinancial.order_trade.entity.v1.MoverType. UI tabs: TOP_GAINER, TOP_LOSER, TOP_VALUE, TOP_VOLUME, TOP_FREQUENCY, IEP/IEV group, IDX_MOVER_DESC/ASC, NET_FOREIGN_BUY/SELL. Default "MOVER_TYPE_TOP_GAINER".
catalog_typeNoWith MOVER_TYPE_CATALOG (stock groups / konglomerat).
filter_stocksNoRepeated key (custom serializer). FILTER_STOCKS_TYPE_SHARIA is used alone ('Syariah Stocks Only'). Default ["FILTER_STOCKS_TYPE_MAIN_BOARD","FILTER_STOCKS_TYPE_DEVELOPMENT_BOARD","FILTER_STOCKS_TYPE_ACCELERATION_BOARD","FILTER_STOCKS_TYPE_NEW_ECONOMY_BOARD"].

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 readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely useful behavior: volume.raw is in lots while values are IDR, and net foreign is session/day-stamped rather than tick-realtime, which prevents misreading the data. It would score higher with rate/pagination-behavior notes rather than a field dump.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The purpose is front-loaded in the first sentence, which is good. But the returns section is a dense, unbroken blob of nested field names that is hard to scan, and it is followed by restated net-foreign caveats already conveyed earlier ('Net foreign is stamped per session' vs the later 'session/day-stamped'), which is redundant.

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 usefully supplies the return shape, units, row count (50), pagination fields and the freshness stamp for net foreign, which is enough for an agent to call and interpret results. Gaps remain around catalog_id/catalog_type usage with MOVER_TYPE_CATALOG and the meaning of the IEP/IEV mover types, which are listed but unexplained.

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%, including enum members, defaults and the repeated-key serializer note for filter_stocks, so the baseline is 3. The description's parameter content largely restates the schema ('and more (mover_type)', default boards) rather than adding new meaning such as interactions between catalog_type and MOVER_TYPE_CATALOG.

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 states a specific resource and scope: ranked stock lists for gainers, losers, most active by value/volume/frequency, and net foreign buy/sell, parameterized by mover_type. This is far more than a restatement of the name. It never distinguishes itself from the visible sibling market_top_stocks, so an agent must guess which ranked-list tool to pick.

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?

The description enumerates list variants and defaults ('Defaults to the main, development, acceleration and new economy boards') but never says when to use this tool rather than market_top_stocks or market_mover_options, nor any prerequisites or exclusions. Guidance is limited to what default applies, not when to call it.

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