Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Realized profit and loss

account_realized_pnl
Read-onlyIdempotent

Retrieve realized gains and losses for closed trades, filtered by stock and period, to review trading performance.

Instructions

Realized gains and losses of closed trades, 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:[...], metadata:{pagination:{cursor:{next}}}}}

Endpoint: GET carina /history/realized.

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

Input Schema

NameRequiredDescriptionDefault
cursorNocursor
periodNoperiod
stock_codeNostock_code
transaction_typesNorepeated key (paramsSerializer indexes:null)

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?

The annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the description only needs to add context — and it does: the trading-session auth requirement, IDR currency, share lots of 100, and the underlying endpoint. The visible return shape including the pagination cursor is a meaningful bonus beyond the annotations.

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?

Four short, front-loaded lines: purpose, prerequisite, units, return shape, endpoint. No filler sentences. The raw endpoint line is the least essential element but is compact and aids error diagnosis.

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 supplies the response envelope and the pagination cursor path, plus the auth prerequisite and unit conventions — enough to call and iterate the tool. The main remaining gap is how the four optional parameters interact (e.g. what `transaction_types` accepts), which is left entirely to the schema.

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%, though the schema's own descriptions merely repeat the property names. The prose adds real meaning for `stock_code` and `period` ('filterable by stock and period') but says nothing about `cursor` or `transaction_types`, which are the two parameters an agent is most likely to get wrong.

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 concrete verb+resource: realized gains and losses of closed trades, filterable by stock and period. It does not name the close sibling account_realized_pnl_detail, so an agent cannot distinguish the summary from the detail view from the text alone, but the core purpose is unambiguous.

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?

It gives a prerequisite (a trading session via `stockbit-mcp login --trading`) and implies the usage context of reviewing closed-trade P&L. There is no explicit when-to-use vs. when-not guidance and no reference to the `_detail` sibling, so the agent must infer which of the two to pick.

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