Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Today's orders

account_orders
Read-onlyIdempotent

Retrieve account order details—including status, side, price, lots, amounts, fees, and amend/cancel eligibility—to verify results of order placement or amendment calls.

Instructions

Orders of the account with status (OPEN, PARTIAL, MATCH, REJECTED, WITHDRAWN …), side, price, lots done/open, amounts and fees, GTC and smart-order details, and what can be amended or cancelled. Use it to confirm the result of order_* calls.

Needs the trading session (stockbit-mcp login --trading). Values IDR; lots of 100 shares.

Returns (Stockbit's data field): {message, data:[{order_id, market_order_id, symbol, status_text (OPEN|PARTIAL|MATCH|REJECTED|PENDING|READY|WITHDRAWN|AMENDED|REQUEST AMEND|REQUEST CANCEL|AMEND CANCELED|ACTIVE|EXECUTED), message (reject reason text), side (SIDE_BUY|SIDE_SELL|SIDE_UNSPECIFIED), time:{order,open,match}, qty:{lot_done,lot_open,lot_total}, price:{order, average:{price,fee}}, amount:{invested,matched,matched_total,open,amount,fee:{amount,open,invested,matched:{amount,broker,exchange}}}, action:{can_amend,can_cancel,amend_target,cancel_target (ACTION_TARGET_*)}, smart_order:{order_id,label,trigger_price,config_type,trailing_stop,bracket_order_children[],parent_id,parent_price,order_type,amount_with_fee,status (ORD…

Endpoint: GET carina /order/v2/list.

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": "account_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
filter_criteria_stock_codeNoFilter by ticker (dotted key, literal)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, but the description adds genuinely non-structured context: the trading-session prerequisite (stockbit-mcp login --trading), the IDR currency, and the lots-of-100-shares convention. That exceeds the annotation bar, though it omits pagination/row limits and result ordering, which matter for a list endpoint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and prerequisites are front-loaded, but roughly two-thirds of the text is a dump of the nested return payload that is truncated mid-token ('status (ORD…'), so it is both bloated and unusable. A short summary of key fields plus a pointer would have earned more per sentence.

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

Completeness4/5

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

With no output schema, describing return fields and status enums is justified, and the auth requirement plus units are exactly the context a caller needs. Remaining gaps are the time scope ('today'), pagination behavior, and behavior when the stock filter is omitted.

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% for the single optional parameter (filter_criteria_stock_code, including the 'dotted key, literal' hint), so the schema already carries the semantics. The description never references the filter at all, so it adds nothing beyond baseline.

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 (account orders) and enumerates concrete returned attributes (status, side, price, lots, fees, GTC/smart-order, amend/cancel flags), which is far more specific than the title alone. It falls short of 5 because the 'today' scope implied by the title is never stated in the description, so an agent cannot tell the time window or how this differs from account_order_detail.

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?

One explicit use case is given: 'Use it to confirm the result of order_* calls.' That is real guidance, but it is narrow — the primary 'list my orders' scenario, the optional stock filter, and any contrast with account_order_detail are left to inference.

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