Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Portfolio summary

account_portfolio_summary
Read-onlyIdempotent

Retrieves your Stockbit account portfolio totals, including equity, invested capital, market value, unrealized and today's gain/loss, and cash balance, in IDR across all portfolios.

Instructions

Totals of the account: equity, invested, market value, unrealized and today's gain/loss, cash.

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

Returns (Stockbit's data field): {message, data:{aggregated_portfolio_summary:, summary_per_portfolios:[{account_number, portfolio_name, summary:}]}}; summary = {trading:{balance}, amount:{invested,allocated,credit_limit}, profit_loss:{net,unrealised,realised}, gain, equity, debt:{ratio,total,market_value,buffer}}.

Endpoint: GET carina /portfolio/v2/summary.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the description is not obliged to repeat that. It instead adds genuinely new behavior: the trading-session login requirement, IDR currency, and the fact that quantities are in lots of 100 shares — all things an agent could otherwise get wrong when interpreting results.

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 returned metrics in the first sentence, followed by prerequisites, units, and return shape. The inline return-shape block is dense but earns its space given there is no output schema; the endpoint path at the end is marginally useful but low-cost.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 fully compensates by describing the response envelope and the nested summary object field by field, plus prerequisites and units. An agent can call this and interpret the response without further documentation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4 and there is nothing schema-side to compensate for. The unit notes (IDR, lots of 100 shares) are the only parameter-adjacent semantics needed, and they are present.

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 resource (account portfolio summary) and enumerates exactly which totals it returns: equity, invested, market value, unrealized and today's gain/loss, cash. An agent knows precisely what data comes back, though it never distinguishes this from the similarly named sibling account_portfolio, leaving the boundary to be inferred.

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 concrete precondition (an active trading session via `stockbit-mcp login --trading`), which is real usage guidance. However, there is no statement of when to prefer this over account_portfolio, account_allocation, or account_performance_* siblings, and no exclusions.

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