Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Withdrawable balance

account_withdrawable
Read-onlyIdempotent

Retrieves the withdrawable cash balance for your Stockbit account in IDR, so you can check funds available for withdrawal without initiating a transaction.

Instructions

Cash that can be withdrawn now (read only; this server never withdraws).

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

Returns (Stockbit's data field): {data:{...withdrawable amounts}} (fields not transcribed).

Endpoint: GET carina /balance/withdrawable.

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

Input Schema

NameRequiredDescriptionDefault
balance_scopeNobalance_scope

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior5/5

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

Goes well past the annotations (which already cover readOnly/idempotent/non-destructive) by disclosing the trading-session auth requirement, the currency (IDR), the share lot size convention of 100, the underlying endpoint, and the shape of the returned data field. These are exactly the operational facts an agent needs and cannot get from structured fields.

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 in the first line, followed by prerequisite, units, return shape, and endpoint in a tight block with no filler. The parenthetical "(fields not transcribed)" is slightly noisy but honestly signals an incomplete return spec rather than padding.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers auth, units, lot conventions, and endpoint for a single-parameter read tool with no output schema, which is close to sufficient. The gap is the sole parameter: an agent has no idea what values balance_scope accepts or whether omitting it is safe, and scope semantics (per sub-account? per currency?) are unstated.

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 coverage is nominally 100%, but the single parameter's schema description is just the string "balance_scope", and the description text never mentions it at all, so no real meaning is added from either source. High coverage sets the baseline at 3; nothing here pushes it above that.

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 qualifier: "Cash that can be withdrawn now," which is meaningfully narrower than a generic cash balance, and it explicitly disclaims being a withdrawal action ("this server never withdraws"). It does not name a sibling (e.g., account_cash vs account_buying_power), so differentiation is left implicit.

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 prerequisite — "Needs the trading session (stockbit-mcp login --trading)" — which is actionable setup guidance an agent would otherwise miss. However, it never says when to pick this over the many sibling balance tools, nor any when-not condition beyond the read-only disclaimer.

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