Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Trading performance

account_performance_trades
Read-onlyIdempotent

Retrieve win rate and profit/loss per stock over a period to assess trading performance and identify stocks that drove account results.

Instructions

Win rate and P/L of trades per stock over a period.

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

Returns (Stockbit's data field): {data:{performance_rating:{total_tpv,total_order,win_rate,total_trade,...}, most_traded_stocks[], ...}}

Endpoint: GET carina /history/performance/trade.

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": {
      "period": "<period>",
      "show_all_stocks": "<show_all_stocks>"
    },
    "name": "account_performance_trades"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodYesperiod
period_endNoperiod_end
period_startNoISO UTC 'YYYY-MM-DDT00:00:00Z' when PERIOD_CUSTOM
show_all_stocksYesclient always sets true

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/non-destructive, and the description adds real behavioral context beyond them: a required authenticated trading session, IDR currency, share quantities in lots of 100, and the underlying endpoint. Missing only rate-limit or freshness/timing behavior.

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 lines. The embedded JSON return snippet is dense but earns its place as the only return-value documentation, since no output schema exists.

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 spends space on the return fields (performance_rating, most_traded_stocks) plus auth, currency, and lot-size caveats — all things an agent would otherwise get wrong. It stops short of enumerating valid period values, a minor gap.

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%, so the baseline is 3. The description's 'over a period' hints at the period/period_start/period_end relationship but adds no syntax or format meaning beyond what the schema already documents, including the ISO format and PERIOD_CUSTOM note.

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 and metrics: 'Win rate and P/L of trades per stock over a period.' An agent can tell this is a per-stock trade performance report, distinct from sibling aggregate tools like account_performance_cumulative or account_performance_return, though the description never explicitly contrasts them.

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?

Gives one hard prerequisite ('Needs the trading session (stockbit-mcp login --trading)') which is genuinely useful usage context, but offers no when-to-use vs when-to-prefer-another guidance against the several sibling performance tools. The scoping ('per stock over a period') implies the use case without stating it.

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