Skip to main content
Glama
INo-xious

stockbit-mcp

by INo-xious

top_movers

Fetch top gainers, losers, or most-active IDX stocks to identify market movers and trading trends.

Instructions

Top gainers, losers, or most-active IDX stocks (hotlist). Returns an empty list when the market is closed — that is expected, not an error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesWhich hotlist
limitNoDefault 25
Behavior4/5

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

With no annotations provided, the description carries the transparency burden. It adds a valuable behavioral note that an empty list is expected when the market is closed, preventing the agent from misinterpreting it as an error. Other behaviors like authentication or rate limits are omitted, but the tool is a simple read-only hotlist, so this is adequate.

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

Conciseness5/5

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

The description is extremely concise: two sentences, with the purpose front-loaded and a key edge case in the second sentence. Every word earns its place; no filler or redundancy.

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?

The combination of schema (100% parameter coverage) and description covers the tool's purpose, its key edge case, and invocation parameters. It does not explain ordering or differentiate from the 'trending' sibling, but these are minor gaps for a tool of this simplicity.

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 coverage is 100% and each parameter has a description, including the enum for 'type' and the default for 'limit'. The tool description adds no additional semantic meaning beyond what the schema already provides, so the baseline 3 is appropriate.

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?

The description clearly states the tool returns a hotlist of IDX stocks categorized as top gainers, losers, or most-active. This specific verb-resource pairing distinguishes it from siblings like 'trending' or 'quote'.

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

Usage Guidelines3/5

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

The intended usage is implied: fetch market movers by category. However, there is no explicit guidance on when to use this tool versus alternatives such as 'trending' or 'quote', nor any exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/INo-xious/stockbit-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server