Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Portfolio positions

account_portfolio
Read-onlyIdempotent

Retrieve all portfolio holdings with lots, average and last prices, market value, and unrealized gain/loss to review positions and performance.

Instructions

Every stock held: lots (total, available to sell), average price, last price, market value, unrealized gain/loss and percent.

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

Returns (Stockbit's data field): {message, data:{smart_order_info:{can_create, info, day_trade_can_create}, summary:{trading:{balance}, amount:{invested, allocated, credit_limit}, profit_loss:{net, unrealised, realised}, gain, equity, debt:{ratio,total,market_value,buffer:{value,percentage}}}, results:[{symbol, company:{name,icon_url}, qty:{stock_on_hand, available:{lot,share}, balance:{lot,share}, unsettled:{lot,share}, unsettled_until_at:{year,month,day}}, price:{latest, average:{price,fee}}, asset:{unrealised:{market_value,profit_loss,gain}, amount_invested}, flags:{allow_order,have_smart_order,can_buy,can_sell,allow_market_order}, exercise:{active,type,price,date:{listing,expired,mature,start,end},info}, type, is_sharia…

Endpoint: GET carina /portfolio/v2/list.

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

Input Schema

NameRequiredDescriptionDefault
acc_noNoinferred: optional account filter (used in query key)
stock_scheduleNoinferred optional
margin_collateral_eligibleNoinferred optional

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description adds the auth requirement (trading session), the currency (IDR), and the unit convention (lots of 100 shares), which are exactly the behavioral details annotations cannot express. It stops short of describing pagination or failure modes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is well front-loaded and earns its place, but the bulk of the description is a raw, truncated dump of the response object that cuts off mid-field ('is_sharia…'). That dump is verbose and structurally noisy rather than a distilled summary of the return shape.

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 carries the burden of explaining return values, and it does attempt a full field map plus auth, currency, and unit context. The attempt is undermined by truncation and by the unexplained optional parameters, but the essential information an agent needs to call and interpret this tool is present.

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 three optional parameters are already documented in the schema (albeit as 'inferred'). The description adds no meaning about acc_no, stock_schedule, or margin_collateral_eligible, so the baseline 3 applies.

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 opening sentence names a specific resource and enumerates the exact fields returned (lots total/available, average price, last price, market value, unrealized P/L and percent), so an agent knows precisely what this returns. It does not explicitly distinguish itself from the singular sibling account_position or account_portfolio_summary, which keeps it from a 5.

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 states a real prerequisite — a trading session via 'stockbit-mcp login --trading' — which is genuinely useful context for when the call will succeed. However, there is no guidance on when to choose this over account_position or account_portfolio_summary, and no statement of when not to use 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