Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Transaction history

account_history
Read-onlyIdempotent

Retrieve past Stockbit trades, deposits, withdrawals, and dividends, filtered by stock and period. Use it to review and audit account transaction records.

Instructions

Past transactions (trades, deposits, withdrawals, dividends …), filterable by stock and period.

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

Returns (Stockbit's data field): {data:{history:[{history_list:[{command (BUY|SELL|DEPOSIT|WITHDRAW|DIV|EXC|IPO|...), ...}]}], meta:{max_page}}}

Endpoint: GET carina /history.

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_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoinferred
pageNo1-based
limitNolimit
startNoinferred (custom range)
stockNostock
periodNoUI uses 'all','1 month','3 month','1 year','3 year','ytd','custom' labels; wire value not confirmed
keywordNoinferred

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior5/5

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

Annotations already declare a safe read (readOnlyHint, idempotentHint, destructiveHint=false), and the description adds substantial context beyond them: a session/login prerequisite, currency (IDR) and unit convention (lots of 100 shares), the response envelope including meta.max_page for pagination, and the underlying endpoint. That is exactly the kind of operational detail annotations cannot express.

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?

Front-loaded with purpose, then prerequisite, units, and return shape in short labeled lines; almost nothing wasted. The ellipsis in the transaction-type list and the terse "GET carina /history" are slightly cryptic but compact.

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, the description correctly compensates by sketching the return structure and page metadata. Given 100% schema coverage, remaining gaps are minor, though the ambiguous period values and start/end relationship are unresolved anywhere.

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%, so all seven parameters are already documented, and the description adds only the framing that filtering happens by stock and period. It offers no clarification of the ambiguous period wire value, which the schema itself flags as unconfirmed, nor of start/end versus the custom period.

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?

States a specific resource (past transactions) with an enumerated list of transaction types and the two filtering axes (stock, period). It is clearly distinct from a detail view, though it never names account_history_detail or explains when that sibling is the better choice.

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 enumeration of transaction types and by the explicit prerequisite ("Needs the trading session (stockbit-mcp login --trading)"), which is useful context. However, there is no when-to-use vs when-not guidance and no routing to alternatives such as account_history_detail or broker_activity_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