Skip to main content
Glama
stockbit-mcp

stockbit-mcp

IHSG price and volume by board

price_by_board
Read-onlyIdempotent

Fetches one day's IHSG composite index level, volume, and value split by regular, cash, and negotiated boards, enabling market-wide board comparison from a single query.

Instructions

One day's IHSG (composite index) level, volume and value split by board (regular, cash, negotiated), as on the home market card. Use symbol IHSG.

volume is shares; values IDR. Stockbit answers an empty result (markets: []) for stocks such as BBCA and for COMPOSITE (checked 2026-10-29); for a stock use price_history or price_ladder.

Returns (Stockbit's data field): data{symbol, date, is_open_market, markets[{board, previous, lastprice, change, percentage_change, open, high, low, frequency, volume (shares), value (IDR)} each {raw,formatted}]}.

Endpoint: GET exodus /company-price-feed/prices/{symbol}/market.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>",
      "date": "<date>"
    },
    "name": "price_by_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesTrading date.
boardsNoRepeated key; UI always sends all four. Default ["MARKET_BOARD_ALL","MARKET_BOARD_REGULER","MARKET_BOARD_TUNAI","MARKET_BOARD_NEGO"].
symbolYessymbol

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, non-destructive behavior. The description still adds real value: the empty-result quirk verified on a specific date, the endpoint path, and the exact return shape (data{symbol, date, is_open_market, markets[...]}). It does not, for example, explain timezone or market-holiday behavior for the date parameter, but the coverage is strong.

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 purpose is front-loaded in the first sentence, and the cautions plus alternatives follow. The dense one-line return-shape spec and endpoint are useful because no output schema exists, though they slightly hurt readability and feel less refined than the rest.

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 three parameters, the description covers return structure, units (shares for volume, IDR for value), edge-case behavior, the underlying endpoint, and the sibling alternatives. Nothing material is missing for an agent to call it correctly.

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 description coverage is 100%, so a baseline of 3 is warranted. The description goes beyond the schema by pinning the symbol parameter to IHSG and clarifying that the result is for one trading day, while grouping boards to regular, cash, and negotiated, which supports the enum values in the schema.

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?

States a specific verb and resource: one day's IHSG composite index level, volume and value split by board, mirroring the home market card. It immediately establishes the scope and the required symbol (IHSG), which distinguishes it from the sibling price tools.

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 says to use symbol IHSG and warns that Stockbit returns an empty result (markets: []) for stocks such as BBCA and for COMPOSITE, directing stock queries to price_history or price_ladder instead. This tells an agent both when to use it and when not to, plus which alternative to pick.

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