Skip to main content
Glama
stockbit-mcp

stockbit-mcp

One order

account_order_detail
Read-onlyIdempotent

Retrieves full details of a single Stockbit order by ID, including match times, smart order triggers, average price, and rejection messages. Use it to inspect or verify one trade order in a trading session.

Instructions

Full detail of one order by id, including match times and rejection message.

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

Returns (Stockbit's data field): {data:} same family as list item but time:{ordered_at,opened_at,matched_at}, time_utc:{ordered_at,opened_at,matched_at,gtc_expired_at}, smart_order.id, smart_order.volume_trigger_order:{trigger_volume,evaluation_price}, price.average.portfolio (UI maps to list shape via orderDetailAPITransform).

Endpoint: GET carina /order/v2/detail.

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": {
      "order_id": "<order_id>"
    },
    "name": "account_order_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_idYesorder_id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses an authentication prerequisite ('Needs the trading session'), currency and share-lot semantics ('Values IDR; lots of 100 shares'), and detailed return-field structure. These are important operational details not captured by readOnlyHint or the input schema.

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, and the remaining sections are organized by prerequisite, units, return shape, and endpoint. Some detail, such as the UI mapping note via orderDetailAPITransform, is extraneous, but most content serves the agent.

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, the description appropriately explains the returned data structure, including nested time fields and smart order details. It also covers the trading-session requirement and units, making it complete enough to call the tool correctly.

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 coverage is 100% for the single parameter order_id, so the schema already documents it fully. The description adds no format or sourcing guidance beyond confirming that the tool looks up by id, which is the baseline for high-coverage schemas.

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 first sentence states a specific verb and resource: 'Full detail of one order by id, including match times and rejection message.' It clearly scopes the tool to a single order and distinguishes it from list-style siblings like account_orders.

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?

The description gives clear context for when to use it: retrieving full detail for one order by id. It does not explicitly name alternatives or state when not to use it, but the single-order scope is unambiguous.

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