Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Cash on hand

account_cash
Read-onlyIdempotent

Retrieve the available cash balance in the RDN account and check buying power for rights issues after trading-session login.

Instructions

Cash available in the RDN account.

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

Returns (Stockbit's data field): {message, data:{available_cash_on_hand:int IDR}}. Buying power for RIGHT issues.

Endpoint: GET carina /balance/cash.

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

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?

The annotations already disclose read-only, idempotent, open-world, and non-destructive behavior. The description adds meaningful context beyond that: authentication requirement, IDR currency, the return shape, and the underlying endpoint. It still lacks failure-mode or rate-limit details, so it is not fully exhaustive.

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?

The description is front-loaded with the main purpose and then separates prerequisites, units, return shape, usage note, and endpoint. It is generally efficient, though phrases like 'lots of 100 shares' are slightly cryptic in a cash-balance context.

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?

For a zero-parameter read tool with rich annotations but no output schema, the description supplies the key missing pieces: authentication needs, currency/unit context, return shape, and endpoint. An agent has enough information to invoke it correctly and interpret the response.

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 there is no parameter semantics to explain. Per the schema baseline for a zero-parameter tool, a 4 is appropriate.

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 clearly states the specific resource: cash available in the RDN account. The note about buying power for RIGHT issues adds scope beyond a generic cash balance, though it does not explicitly position itself against siblings such as account_buying_power or account_withdrawable.

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 names an important prerequisite: the trading session must be authenticated via `stockbit-mcp login --trading`. It also implies usage for RIGHT-issue buying power, but does not explicitly state when to use this tool versus related balance or buying-power siblings.

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