Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Realized P/L detail

account_realized_pnl_detail
Read-onlyIdempotent

Fetch the individual stock, bond, and coupon trades behind a realized P/L entry by date, narrowed by symbol or history ID, to verify how gains or losses were calculated.

Instructions

The trades behind one realized P/L entry.

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

Returns (Stockbit's data field): {data:{stock_realized:{trades}, bond_realized:{detail}, coupon_realized:{detail}}}

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

Input Schema

NameRequiredDescriptionDefault
dateYesYYYY-MM-DD
symbolNosymbol
history_idNohistory_id

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 safety is covered. The description adds genuinely useful behavior beyond that: a required trading-session prerequisite, IDR currency, lot size of 100 shares, and the concrete return shape — all of which affect how results should be interpreted.

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 the core purpose, then prerequisites, units, and return shape in short digestible lines. The raw 'Endpoint: GET carina /history/realized/detail' line is operational trivia that contributes little for an agent, a minor waste.

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?

The tool is a simple read with three params and no output schema, and the description covers the key missing pieces: session requirement, currency/lot units, and the structure of the returned data field. It could be stronger on how to obtain a valid history_id, but it is largely complete for this complexity.

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%, hitting the baseline of 3, but the schema's own descriptions are nearly tautological ('symbol', 'history_id'). The description implies an entry is identified via the P/L entry but doesn't explain how history_id, date and symbol combine, so it adds little parameter meaning.

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 first sentence states a specific resource — the underlying trades of a single realized P/L entry — which clearly distinguishes it as a drill-down from the aggregate account_realized_pnl, even without naming the sibling explicitly. A verb is implicit (retrieve trades), so it's clear but not maximally sharp.

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?

The description supplies a concrete prerequisite (an authenticated trading session via 'stockbit-mcp login --trading'), which tells the agent when this call is viable. However, it never states when to use this instead of the aggregate realized P/L tool or which argument selects the specific entry, leaving the selection logic 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