Skip to main content
Glama
stockbit-mcp

stockbit-mcp

One transaction

account_history_detail
Read-onlyIdempotent

Fetch details for one Stockbit account history entry by ID and ISO date, returning action details and IDR values so you can review or reconcile a specific trade record.

Instructions

Detail of one history entry.

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

Returns (Stockbit's data field): {data:{action_detail, ...}}

Endpoint: GET carina /history/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": {
      "id": "<id>",
      "date": "<date>"
    },
    "name": "account_history_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesid
dateYesISO timestamp

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real context beyond that: the authentication prerequisite (trading session login), that values are in IDR, that share quantities are in lots of 100, and the general response shape via Stockbit's data field. Only the endpoint line adds little.

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?

Short, front-loaded, and organized into distinct lines for purpose, prerequisite, units, and return shape. The 'Endpoint: GET carina /history/detail' line is the only sentence that does not clearly earn its place for an agent choosing and calling the tool.

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?

For a 2-parameter read tool with no output schema, the description supplies the missing pieces: auth requirement, currency and lot-size units for interpreting results, and a sketch of the return payload. The remaining gap is the meaning of the required id and its relationship to date, which neither the description nor the schema resolves.

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%, but the schema's own descriptions are bare ('id', 'ISO timestamp'). The description adds no clarification of what the id identifies (history entry vs order) or whether the date must match the entry, so it neither compensates nor regresses. Baseline 3 applies.

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 description states a specific verb and resource: 'Detail of one history entry,' which distinguishes it from a list-style sibling like account_history by scope (one vs many). It does not explicitly distinguish itself from account_order_detail or account_realized_pnl_detail, which are the closest competing 'detail' tools, so it stops short of a 5.

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 implied by the word 'detail' plus a hard prerequisite: 'Needs the trading session (stockbit-mcp login --trading).' That prerequisite is genuinely useful, but there is no explicit statement of when to pick this over account_order_detail or account_history.

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