Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Order book and quote

price_orderbook
Read-onlyIdempotent

Fetch live quote and order book data for a stock symbol, including last price, change, high/low, bid/offer levels, and pre-opening IEP/IEV indicators.

Instructions

Live quote and order book of one symbol: last price, change, open/high/low, previous close, ARA/ARB limits, bid and offer levels with lots and frequency, IEP/IEV in pre-opening.

bid[].volume and offer[].volume are SHARES (divide by 100 for lots); total_bid_offer.raw_lot is shares too despite its name; iepiev quantities are lots. Prices IDR.

Returns (Stockbit's data field): {data:{lastprice, previous, open, high, low, close, change, percentage_change, bid:[{price,que_num,volume,change_percentage}], offer:[...], status, tradable, uma, notation[], ara:{value (string, ',' thousands),visible}, arb:{value,visible}, next_ara, next_arb, autoreject_time_left_in_sec, auto_reject_estimation:[{value,change_to_prev:{value,percentage},change_to_base:{value,percentage},type (AUTO_REJECT_TYPE_POSITIVE|NEGATIVE|BASE)}], iepiev:{status,iep,iev,time_left_seconds,best_bid_offer:{bid:{price:{raw},quantity},offer:{...}}}, total_bid_offer, company_type, corp_action, ...}, message}

Endpoint: GET exodus /company-price-feed/v2/orderbook/companies/{symbol}.

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>"
    },
    "name": "price_orderbook"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNolimit
symbolYessymbol
directionNodirection
with_full_price_tickNowith_full_price_tick

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered; the description instead contributes genuinely non-obvious operational context. It warns that bid[].volume and offer[].volume are SHARES despite the raw_lot naming, that iepiev quantities are lots, and that prices are IDR — the kind of gotcha that causes real misinterpretation. It also names the concrete endpoint, though it says nothing about rate limits or empty-result behavior.

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 statement is front-loaded, and the high-value unit and currency caveats are placed before the bulky return blob. The pseudo-JSON return sketch with '...' and deep nesting is dense and slightly unwieldy, but with no output schema present it is doing necessary work rather than padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description rightly spends most of its length on the return payload, units, and currency, which makes it largely self-sufficient for interpreting results. However it leaves the three optional parameters (limit, direction, with_full_price_tick) completely unexplained and does not say how many bid/offer levels come back or how the pre-opening versus open status affects field availability.

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 reported at 100%, so the schema is nominally the source of truth and a baseline of 3 applies. In practice the description adds nothing about limit, direction, or with_full_price_tick — an agent gets no help on whether limit caps bid/offer depth, what direction controls, or when to request full price ticks. Only the symbol parameter's meaning is made clear, and that comes from the prose scope statement.

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 opening sentence names the resource (live quote and order book), constrains scope to a single symbol, and enumerates the specific fields returned (last price, ARA/ARB, bid/offer levels, IEP/IEV in pre-opening). An agent can immediately tell this is the deep per-symbol book view rather than a market-wide or historical feed. It loses a point because it never names a sibling such as price_latest or price_snapshot to differentiate when the shallow quote is enough.

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?

Usage is only implied by the content description: you would reach for this when you need full depth-of-book plus quote limits for one symbol. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative tool for simpler quote needs. The pre-opening IEP/IEV mention hints at a market-state condition but is not framed as guidance.

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