Skip to main content
Glama
INo-xious

stockbit-mcp

by INo-xious
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

top_movers

Read-only

Retrieve Stockbit's curated hotlist of top gainers, losers, or most active stocks. The list is a fixed nine-symbol set, not a market-wide ranking, and returns empty when the market is closed.

Instructions

Stockbit's HOTLIST — a small curated list, NOT a market-wide ranking. Use market_movers for the market-wide one. This matters because the two look interchangeable and are not. Measured 2026-09-01, every call to this hotlist returned the SAME NINE symbols — at limit 5, 25, 50 and 100 alike. limit is sent and the service ignores it. So the ranking you get is a correct ordering over a nine-symbol universe, not the top of the exchange, and reading it as 'today's top gainers on IDX' overstates it by a wide margin. That also disposes of a reported bug: a contiguous descending run of nine changes is what a correct sort over nine symbols looks like. There is nothing wrong with the ordering; the universe is simply small, and this description is the fix. market_movers reads a different service and returned 50 rows for the same moment, including structured warrants. The two disagreeing is expected and is not evidence that either is wrong. Returns an empty list when the market is closed — that is expected, not an error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesWhich hotlist
limitNoSent, but the service ignores it — nine rows come back regardless. Default 25.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.0
    • changedInput schema / properties / limit / description
      Previous value: -"Default 25"New value: +"Sent, but the service ignores it — nine rows come back regardless. Default 25."
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnly/openWorld/destructive annotations, the description discloses important behavior: the service ignores limit, always returns the same nine-symbol universe, returns an empty list when the market is closed, and is not buggy despite appearing so. This is rich, non-obvious context that materially changes how an agent should interpret results.

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 description is front-loaded and logically organized, but it is longer than needed. The empirical measurement narrative and bug-report digression could be condensed into a few crisp statements without losing the critical warnings.

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?

For a tool with no output schema, the description covers the main behavioral risks: limited universe, ignored limit, empty response on closed market, and sibling expectations. It stops short of describing the exact return row structure, but the mention of nine symbols and descending changes gives enough context for correct use.

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?

The schema already documents both parameters, including that limit is ignored. The description adds further semantic weight by explaining that every tested limit value still returned the same nine symbols, making the ignored-limit behavior concrete and hard to miss. It does not add much about the type parameter, but the schema covers it well.

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 clearly identifies the resource as "Stockbit's HOTLIST" and immediately signals it is NOT a market-wide ranking, naming market_movers as the alternative. However, it never explicitly states an action like "returns top gainers/losers/most active," relying partly on the tool name and schema enum for that detail.

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?

The description gives explicit usage guidance: "Use market_movers for the market-wide one." It also tells the agent when an empty list is expected, explains why disagreement with market_movers is normal, and warns against interpreting the hotlist as exchange-wide movers.

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