Skip to main content
Glama
INo-xious

stockbit-mcp

by INo-xious

market_movers

Read-only

Get the market-wide movers ranking from Stockbit with views for top gainers, losers, value, volume, frequency, net foreign buy/sell, and big money. Use for a broader universe than the hotlist.

Instructions

The market movers behind Stockbit's own Movers dialog — the market-wide ranking. This is a DIFFERENT endpoint from top_movers, which reads the hotlist, and the difference is not cosmetic: measured 2026-09-01, the hotlist served NINE symbols while this served FIFTY, including structured warrants. Different universes. A symbol in one and not the other is expected, and a disagreement is not evidence that either is wrong. For a market-wide ranking, this is the one to use. view selects the tab, and the vocabulary is CLOSED to the eight members the server was seen to accept: topGainer, topLoser, topValue, topVolume, topFrequency, netForeignBuy, netForeignSell, bigMoneyNetValue. Each was echoed back verbatim on 2026-09-01, against a control value that answers 400 — so this endpoint rejects members it does not know rather than silently serving its default, which is what makes the echo trustworthy. The result's view is that echo: what the server says it SERVED, not what you asked for. The UI's ninth tab, IEP/IEV, is NOT a view — ten spellings of it were refused. It is a field: every row carries iepIev with the indicative equilibrium price and volume. Those are only meaningful during pre-opening (08:45-09:00 WIB) and read zero outside it. limit is honoured, but the service caps the answer at 50 rows however large it is. page is ignored, and the payload's own pagination block reads all zeros on every call, so it is not reported rather than passed through as a fake answer about whether more rows exist. Every row carries readFrom naming the wire key each value came from, unmappedKeys for anything this projection does not recognise, and the raw row. foreign says which session the net-foreign figures are from. foreign.isShown is the service's own flag for whether they mean anything yet: it reads false intraday and true after the ~18:00 WIB broker release on the same day. Foreign figures carrying yesterday's date before that release are correct and unpublished, not stale. An empty list is normal outside trading hours, though this endpoint served 50 rows with the market shut.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
viewNoWhich tab. Omitted takes the server's default view — read `view` to see which.
limitNoMax rows. Honoured, but capped at 50 by the service. Omitted takes its default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already mark readOnlyHint=true and destructiveHint=false, but the description adds substantial behavioral detail beyond that: the server caps `limit` at 50, ignores `page`, returns a `view` echo reflecting what was served, rejects unknown view members with 400, and has meaningful state semantics for `iepIev` and `foreign.isShown`. It even explains when empty results are expected. No contradiction with annotations.

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 description is long, but nearly every sentence earns its place by revealing hard-won behavioral facts that are not available from the schema or annotations. It is front-loaded with the core purpose and sibling distinction, then moves into parameter semantics and timing edge cases. Slightly dense, but not padded.

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 tool with no output schema, the description is unusually complete: it covers the full `view` vocabulary, server rejection behavior, limit cap, ignored `page`, zeroed pagination block, foreign session timing, pre-opening semantics, and normal empty results. An agent has everything needed to call this tool correctly and interpret its response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents both parameters. The description goes well beyond that by fixing the `view` vocabulary to eight accepted members, warning that ten IEP/IEV spellings were refused, and stating that `limit` is honored but capped at 50. It adds behaviorally important semantics like the echo behavior and the meaning of omitted `view`.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific, unambiguous statement: it is the market-wide ranking behind Stockbit's Movers dialog. It names the sibling it is not (top_movers), explains the operational difference (hotlist vs market-wide, 9 vs 50 symbols), and closes with a direct routing instruction. No ambiguity remains about what resource this tool addresses.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly contrasts with top_movers: 'the hotlist served NINE symbols while this served FIFTY' and states 'For a market-wide ranking, this is the one to use.' It also tells the agent when an empty list is normal, and describes the closed vocabulary of `view` values. This gives clear selection criteria versus the sibling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.