Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Quote snapshot of many symbols

price_snapshot
Read-onlyIdempotent

Fetch price snapshots for up to 100 IDX symbols in one call, including last price, change, open/high/low, volume, value, foreign flow and ARA/ARB. Use it to check watchlists and portfolios quickly.

Instructions

One call for up to 100 symbols: last price, change, open/high/low, previous close, volume, value, frequency, foreign buy/sell/net and foreign vs domestic share, status, notations, ARA/ARB. For watchlists and portfolios; use price_orderbook for one symbol's bid and offer levels.

value, fbuy, fsell, fnet and net_foreign are IDR; foreign and domestic are percentages. bid and offer are null here.

Returns (Stockbit's data field): data[{symbol, name, lastprice, previous, open, high, low, close, change, percentage_change, volume, value, frequency, average, fbuy, fsell, fnet, net_foreign, foreign, domestic, status, tradeable, notation[], uma, corp_action, ara, arb, iepiev, company_type}]

Endpoint: GET exodus /orderbook/companies.

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": {
      "symbols": "<symbols>"
    },
    "name": "price_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsYesIDX tickers; the app asks for at most 100 per call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description still adds real behavioral detail beyond them — the 100-symbol batch limit, per-field units (IDR for value/fbuy/fsell/fnet/net_foreign, percentages for foreign/domestic), the fact that bid/offer are null in this response, and the backing endpoint. It does not discuss rate limits or failure behavior for invalid tickers.

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?

Content is front-loaded: scope first, then usage/routing, then units, then the return field list. The long field enumeration is justified because no output schema exists, but the notation is dense (terse field names in one run-on block) and slightly harder to scan than the opening sentences.

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 one-parameter batch-read tool with no output schema, everything an agent needs is present: the batch limit, the unit conventions that would otherwise cause misinterpretation, the null-field caveat, and the full returned field set. Nothing required for a correct call is left to inference.

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 description coverage is 100% and the single parameter already carries its own description including the 100-item cap and IDX ticker meaning. The description's 'up to 100 symbols' restates the schema rather than adding new semantics such as ticker format examples or duplicate handling, so the baseline 3 applies.

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 opens with a concrete verb-like statement of scope ('One call for up to 100 symbols') and immediately enumerates the resource contents (last price, change, OHLC, previous close, volume, foreign flows, ARA/ARB). It also explicitly distinguishes itself from price_orderbook, so an agent can separate it from the nearest sibling without opening any schema.

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 an explicit use context ('For watchlists and portfolios') and names an alternative with the selecting condition ('use price_orderbook for one symbol's bid and offer levels'), reinforced by 'bid and offer are null here'. It stops short of distinguishing other likely price siblings, but the one routing decision that matters most is stated outright.

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