Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Sub-accounts

account_sub_accounts
Read-onlyIdempotent

Retrieve Stockbit sub-account portfolios (regular, syariah, day-trade, margin) with account status and balances; requires an authenticated trading session.

Instructions

The account's portfolios (regular, syariah, day-trade, margin) and their balances.

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

Returns (Stockbit's data field): {data:{regular:{accounts:[{account_number, account_status (ACCOUNT_STATUS_*), is_main_account, portfolio_info:{portfolio_name,purpose (PURPOSE_*)}, balance_info:{component_name,value}, is_linked_to_advisor, ifa_permission:{stock_transfer_in,stock_transfer_out,cash_transfer_in,cash_transfer_out,withdrawal}}], can_create_new_account, can_not_create_new_account_reason:{type,title,description}}, margin:{same}}}

Endpoint: GET carina /v2/sub-account/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_sub_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
balance_info_options_stock_codeNobalance_info_options.stock_code
balance_info_options_should_includeNoqs allowDots serialization

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 readOnlyHint, idempotentHint and openWorldHint, so the description is not carrying the safety profile. It adds material context beyond that: a required authenticated trading session, values denominated in IDR, share quantities in lots of 100, and the full shape of the returned data including account_status and purpose enums.

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?

Purpose is front-loaded, followed by prerequisites, units, and the return shape. The return block is a dense JSON sketch that earns its space because no output schema exists, though the inline type/enum notation is heavier than strictly needed.

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 compensates by documenting the return structure, and it supplies the authentication prerequisite and unit conventions an agent needs. Only the relationship to sibling account-listing tools is left out.

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 both parameters (balance_info_options_stock_code and the allowDots serialization flag) are already documented in the schema. The description mentions 'balance_info' only in the return shape and adds no invocation semantics for either parameter, 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?

States a concrete resource: the account's portfolios (regular, syariah, day-trade, margin) and their balances, and names the upstream endpoint. It is clear what data comes back, though it never contrasts itself with siblings such as account_portfolio or account_position, so an agent must infer the boundary.

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 a real precondition (requires the trading session, installed via stockbit-mcp login --trading), which is genuine usage guidance. It says nothing about when to choose this over the other account_* listing tools, so the when-to-use half is only implied.

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