Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Order queue at a price

flow_order_queue
Read-onlyIdempotent

Retrieve individual bid or offer orders waiting at a chosen price level for a stock, with lots, timestamps, broker details, and status, to inspect order book queue depth.

Instructions

The queue of individual orders waiting at one price level (bid or offer), with their lots and time, for one symbol. Use the order book first to pick the price.

Volumes (lot, blot, slot) are in lots of 100 shares; values are IDR.

Returns (Stockbit's data field): data{is_open_market, pagination{has_next_page}, orders[{id, queue_number '1', stock_code, time ISO8601, action_type, price, status ORDER_STATUS_*, open (lots remaining), lot (lots), queue_lot, board_type, broker_code, broker_group BROKER_GROUP_*, exchange_order_number{full '', formatted '5308276'}, order_number}]}.

Endpoint: GET exodus /order-trade/order-queue.

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": {
      "stock_code": "<stock_code>"
    },
    "name": "flow_order_queue"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNolimit Default 100.
priceNoPrice level; needed for queue paging and WS live updates. Unit: IDR.
sort_byNosort_by
board_typeNoboard_type Default "BOARD_TYPE_REGULAR".
stock_codeYesTicker.
action_typeNoBid vs offer queue. Default "ACTION_TYPE_ALL".
order_statusNoorder_status Default "ORDER_STATUS_OPEN".
sort_directionNoFirst click on a column = ASC.
filter_time_endNoLiteral dotted key. Unit: HH:mm.
filter_time_startNoLiteral dotted key. Unit: HH:mm.
jump_exchange_order_numberNoJump to own order.
last_exchange_order_numberNoNext page cursor = orders[-1].exchange_order_number.full.
first_exchange_order_numberNoPrevious page cursor = orders[0].exchange_order_number.full.
search_exchange_order_numberNoFind a specific exchange order number (short 'formatted' form, e.g. 5308276).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, non-destructive, and open-world, so safety is covered. The description adds real context beyond them: lot units of 100 shares, IDR values, and the endpoint. Its main extra value is the full return shape, since no output schema exists, but it says nothing about paging limits, live-update behavior, or rate limits.

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?

It is front-loaded with the purpose, then the units, then the return shape, then the endpoint. The dense inline dump of return fields is long but justified because there is no output schema. Minor cost: the field enumeration reads as raw spec text rather than prose.

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 14-parameter read tool with no output schema, the description covers what the agent needs: the prerequisite for the price parameter, the units, the exact return shape, and the endpoint. Nothing essential for correct invocation is missing.

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?

With 100% schema coverage, the baseline is 3, and the description earns above that by tying the price parameter to the paging and live-update workflow and by explaining that volumes are in lots of 100 shares and values in IDR. It also explains how the first and last exchange order numbers act as page cursors by pointing to the returned orders array, which the schema alone doesn't make explicit.

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 names a specific resource and scope: 'the queue of individual orders waiting at one price level (bid or offer), with their lots and time, for one symbol.' That distinguishes it from the sibling order book tool by directing the agent to price_orderbook first, then coming back here for the per-order queue.

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 a clear prerequisite workflow: 'Use the order book first to pick the price,' which tells the agent how to satisfy the practically required price parameter. It doesn't state explicit exclusions, for example when to use running-trade or trade-book views instead of the queue, so it falls short of a 5.

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