Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Market breadth (advancers vs decliners)

market_breadth
Read-onlyIdempotent

Count IHSG stocks that are up, down, and unchanged for live or a past trading day to assess market direction from Stockbit's overview.

Instructions

How many IHSG stocks are up, down and unchanged, live or on a past trading day: the breadth bar of the app's market overview.

Live counts are 0 before the market opens and on non-trading days; pass date for a closed day. Only the IHSG catalog is known to work (LQ45 and IDX30 answered "Catalog not found", 2026-11-18).

Returns (Stockbit's data field): data{catalog_list[{catalog_detail{code, type ('CATALOG_TYPE_INDEX')}, price{up_count, down_count, unchanged_count}, total_stock}]}

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

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

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD trading day; omit for live. Live counts are 0 outside trading hours.
catalog_codesNoCatalog code. The app sends only IHSG; LQ45 and IDX30 answered 'Catalog not found' (2026-11-18). Default "IHSG".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only cover safety (read-only, idempotent, open-world, non-destructive); the description adds real behavioral context on top: the zero-count behavior outside trading hours, the failure mode for LQ45/IDX30 catalogs with a dated observation, and the underlying endpoint. These are exactly the gotchas an agent would otherwise hit blindly.

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 lead sentence delivers purpose first, then caveats, then return shape and endpoint. The returns block is somewhat dense schema shorthand, but with no output schema it earns its place. Minor redundancy between the prose catalog warning and the parameter description.

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?

With no output schema and only two optional parameters, the description covers purpose, edge cases, catalog limitations, live-vs-historical behavior, and the exact return structure. An agent could call this correctly on the first attempt.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema only partly carries: the catalog limitation is reinforced in prose and the date parameter's live-vs-closed-day semantics are tied to the zero-count behavior. It stops short of documenting format/range detail beyond the schema pattern.

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 states a concrete resource and measurement: counts of IHSG stocks up, down and unchanged, live or on a past trading day, plus the framing 'breadth bar of the app's market overview'. That is far more specific than the name alone. It does not explicitly name a contrasting sibling (e.g. market_movers), so it stops short of full differentiation.

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

Usage Guidelines4/5

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

It gives clear when-to-use rules: omit date for live data, pass date for a closed trading day, and it warns that live counts are 0 before the open and on non-trading days. It also flags that only the IHSG catalog is known to work. No explicit sibling exclusions are offered, but the usage context is unambiguous.

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