Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Buying power

account_buying_power
Read-onlyIdempotent

Check available trading balance, limit, and day-trade or margin buying power in IDR; include stock_code to get per-stock figures before placing orders.

Instructions

Trading balance, trading limit, day-trade buying power and margin buying power. Pass stock_code to get the figures for that stock.

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

Returns (Stockbit's data field): {message, data:{trade_limit, trade_balance, day_trade_buying_power, day_trade_leverage, day_trade_trading_balance, margin:{buying_power,status,trading_balance,total_debt,total_collateral}}} (IDR).

Endpoint: GET carina /balance/cash/info.

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

Input Schema

NameRequiredDescriptionDefault
order_idNoWhen amending: existing order id
stock_codeNoTicker the order is for (day-trade leverage is per stock)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the description's job is to add context – and it does: it discloses the authentication/session prerequisite, the currency (IDR), and the share-lot convention (lots of 100 shares), all of which affect interpretation of returned numbers. It also discloses the payload shape via the returned data field list, which annotations could not convey.

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

Conciseness5/5

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

Front-loads what the tool returns, then the parameter rule, then prerequisites, then the response shape and endpoint. Every line carries distinct information with no filler or repetition.

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?

No output schema exists, but the description enumerates the returned fields, so an agent knows what it will receive; the auth prerequisite and units are also covered. The only loose end is the unexplained order_id parameter, which the description never addresses for what is otherwise documented as a GET read.

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 are already documented and the baseline is 3. The description reinforces the stock_code semantics ('day-trade leverage is per stock') but adds nothing about order_id, which sits in the schema with an 'when amending' note that is incongruous for a read-only GET endpoint.

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?

Names the specific figures returned (trading balance, trading limit, day-trade buying power, margin buying power) and the resource behind them, so an agent can tell this is a read of account buying-power data rather than cash or portfolio holdings. It does not explicitly distinguish itself from near-neighbors like account_cash or account_withdrawable, keeping it short of 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?

Gives a concrete usage rule for the optional parameter ('Pass stock_code to get the figures for that stock') and a prerequisite ('Needs the trading session (stockbit-mcp login --trading)'). It never says when to choose this over sibling balance tools or when it is not appropriate, so the guidance is implied rather than comparative.

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