Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Can these stocks be traded?

account_tradable
Read-onlyIdempotent

Check whether given stock codes are tradable, sharia-compliant, or margin-eligible and which boards (RG, NG, TN) they trade on, so you can filter eligible symbols before trading.

Instructions

For each symbol: tradable, sharia-tradable, margin-tradable, and per board (RG, NG, TN).

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

Returns (Stockbit's data field): {message, data:[{stock_code, is_tradable, is_sharia_tradable, is_margin_tradable, is_nego_tradable, stock_type:{sharia,margin}, board_tradable:{rg,ng,tn}, margin_board_tradable:{rg,ng,tn}}]}

Endpoint: GET carina /stock/tradable.

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": {
      "stock_codes": "<stock_codes>"
    },
    "name": "account_tradable"
  }
}

Input Schema

NameRequiredDescriptionDefault
stock_codesYesSingle code or repeated key stock_codes=A&stock_codes=B

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 cover the safety profile (readOnly, idempotent, non-destructive, open-world). The description goes further by disclosing the required trading-session auth, the unit conventions (IDR, lots of 100 shares), and the exact shape of the returned data field, which matters because there is no output schema.

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?

Four short lines, front-loaded with what is returned and what is required, with no filler prose. The trailing 'Endpoint: GET carina /stock/tradable' is internal routing detail of marginal value to an agent and is the only line that does not earn its place.

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?

For a one-parameter read tool with no output schema, the definition supplies the prerequisite auth, the response payload structure, and the units — enough for an agent to call it and interpret results. Only the absence of alternative-routing guidance keeps it short of complete.

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 100% and the single parameter's batch syntax (stock_codes=A&stock_codes=B) is already documented in the schema. The phrase 'For each symbol' confirms batch semantics and the per-item result mapping, which is a small but real addition over the schema.

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 first line names the resource and the exact dimensions checked (tradable, sharia-tradable, margin-tradable, per board RG/NG/TN), so an agent knows precisely what question the tool answers. It is clearly a per-symbol tradability lookup rather than a portfolio or order tool, though it never names a sibling it should be preferred over.

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?

The prerequisite 'Needs the trading session (stockbit-mcp login --trading)' is a genuinely useful operational condition that tells the agent when the call will fail. However, there is no statement of when to reach for this versus adjacent account/market tools, and no exclusions or failure-mode guidance beyond the session requirement.

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