Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Position in one stock

account_position
Read-onlyIdempotent

Retrieve your Stockbit account's regular and day-trade position for an IDX ticker, including sellable lots, average price, gain/loss, and smart-order eligibility.

Instructions

The position in one symbol, regular and day-trade: lots held and available to sell (qty.available.lot), average price, gain/loss, whether a smart order can be created.

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

Returns (Stockbit's data field): {message, data:{result:<portfolio item|empty>, day_trade:<portfolio item|empty>}} where item = portfolio list item plus can_create_smart_order, info[]. Use qty.available.lot as sellable lots.

Endpoint: GET carina /portfolio/v2/detail.

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_code": "<stock_code>"
    },
    "name": "account_position"
  }
}

Input Schema

NameRequiredDescriptionDefault
acc_noNoinferred optional
stock_codeYesIDX ticker

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds real context beyond that: an authentication prerequisite (trading session login), currency (IDR), and lot sizing (100 shares per lot), plus the endpoint being called. It stops short of stating failure behavior for a missing session or a symbol the user holds no position in.

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?

It is front-loaded with the core purpose and then layers prerequisite, units, return shape, and endpoint in a scannable order. There is mild redundancy: 'use qty.available.lot as sellable lots' appears twice in slightly different phrasing, which costs a little space but no clarity.

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?

With no output schema and only two parameters, the description compensates fully by spelling out the response envelope and the fields inside each portfolio item, including which field to read for sellable quantity. Combined with the auth prerequisite and unit conventions, an agent has everything needed to call and interpret this tool correctly.

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 ('IDX ticker' for stock_code). The description reinforces that stock_code is a single symbol and clarifies it is an IDX ticker context, but adds nothing about acc_no, which the schema labels only as 'inferred optional'. Baseline 3 applies since the schema does the heavy lifting.

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 sentence names a specific resource and scope ('position in one symbol') and enumerates what is returned: lots held/available, average price, gain/loss, and smart-order eligibility. It is clearly a single-symbol detail lookup rather than a portfolio listing, though it never names a sibling such as account_portfolio to make the distinction explicit.

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?

Usage is implied by the single-symbol scope and the stated prerequisite that a trading session is needed ('stockbit-mcp login --trading'), which is genuinely useful gating information. However, there is no explicit statement of when to prefer this over account_portfolio or account_portfolio_summary, so the agent must infer the choice from scope alone.

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