Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Trading limits and status

account_trading_info
Read-onlyIdempotent

Retrieves your Stockbit account's trading rules and limits—day-trade availability, split-order caps, market cycle, order count, and margin status—for order planning.

Instructions

Trading rules for the account now: day-trade availability, split-order limits, market cycle, order count limits, margin status (choose with features).

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

Returns (Stockbit's data field): {message, data:{day_trade:{event_type (EVENT_TYPE_DISABLE_OUTSIDE_MARKET_HOURS|EVENT_TYPE_DISABLE_EXCEED_DEBT_RATIO|EVENT_TYPE_UNSPECIFIED),...}|null, split_order:{remaining_trading_open,remaining_trading_close,trading_open,trading_close,max_order,max_lot_per_order,max_lot_auto_split?}, fix_metadata, cash_sweep, market_cycle:{market_cycle_allocation:{name (ALLOCATION_NAME_*),start_at,end_at}, full_call_auction_cycle:{session_type (SESSION_TYPE_*),session_phase (SESSION_PHASE_*),banner:{formatted_msg}}}, margin_trading, independent_advisor, order_count_limit:{hard_limit, soft_limit:{phase_1,phase_2}, user_order_count, user_daytrade_order_count}}}. Only requested features are populated.

Endpoint: GET carina /trading/info.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "features": "<features>"
    },
    "name": "account_trading_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
featuresYesRepeated key (features=A&features=B, seen in HAR) or comma-joined (features=A,B, used by fast-trade/buy-sell)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds meaningful behavioral context beyond that: the trading-session auth requirement, IDR currency, 100-share lot units, and the crucial 'only requested features are populated' caveat. Return-format detail is present but is largely a raw proto dump rather than a distilled behavioral statement.

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 opening sentence is well front-loaded and states scope fast. The return-value block, however, is a single sprawling inline object with proto enum names and optional-field markers that is hard to scan, and it repeats detail that a machine consumer of the response will get anyway. Given no output schema exists, some of this earns its place, but it is not efficiently structured.

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 one parameter, no output schema, and a single read-only endpoint, the definition covers what an agent needs: auth prerequisite, currency, lot sizing, feature-gated population, and endpoint path. The full response shape is exposed inline, which compensates for the missing output schema. It is close to complete for this tool's complexity.

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?

Schema coverage is 100% and the schema already explains the repeated/comma-joined encoding of 'features', so the baseline would be 3. The description earns an extra point because its enumeration of returned sections (day_trade, split_order, market_cycle, margin_trading, order_count_limit, etc.) effectively telegraphs which feature keys can be requested, plus it states that only requested features are populated — semantics the schema does not carry.

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 names a concrete resource (account trading rules/limits) and enumerates the specific facets returned: day-trade availability, split-order limits, market cycle, order count limits, margin status. That is far more specific than the title alone and lets an agent tell it apart from pure status tools like market_status or session_status, though it never explicitly contrasts itself with a named sibling.

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 supplies a real prerequisite — the trading session must be established via 'stockbit-mcp login --trading' — which is genuine when-to-use context. However, there is no statement of when to prefer this over siblings such as account_buying_power or market_status, and no exclusions; the 'choose with features' line hints at selection but leaves it implicit.

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