Skip to main content
Glama
INo-xious

stockbit-mcp

by INo-xious
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

portfolio

Read-only

Retrieve your actual Stockbit Sekuritas holdings with average price and current value. Use it to assess position sizing and concentration before giving advice, instead of treating a watchlist as holdings.

Instructions

The user's ACTUAL stock holdings at Stockbit Sekuritas — what they own right now, at what average price, and what it is worth. This is the account, not a watchlist: watchlist is a list of symbols someone is following, this is money at risk. Read it before offering any opinion that touches position sizing, concentration or whether to add. An opinion about BBRI means something different to someone holding 40% of their portfolio in it. totals carries the account-level figures from the summary endpoint. If the summary request fails the holdings are still returned and totalsUnavailable says why — do not report the portfolio as unreadable in that case. LOTS AND SHARES: 1 lot = 100 shares. Each is reported only when a wire key whose name says which one carried it; derived lists any that this server computed from the other. A derived figure is arithmetic, not a reading. Requires the trading session (stockbit-auth trading-login). Field mapping is partly verified: nested portfolio totals, empty positions, cash, fees, masked identity, tradability and trading features were checked read-only on 2026-09-24. Nonempty holding, order and history rows remain projected from frontend schemas. readFrom names the fields actually mapped; missing values are not zero.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.2

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, but the description adds substantial behavioral detail: summary-request failure produces `totalsUnavailable` rather than an unreadable portfolio, 1 lot = 100 shares, `derived` values are computed arithmetic, the trading session is required, and field-mapping status is disclosed with `readFrom`. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but every sentence earns its place: purpose, use case, failure semantics, unit conventions, authentication requirement, and data provenance. It is front-loaded with the crucial watchlist distinction and does not waste words on annotation repetition.

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?

Even without an output schema, the description covers return semantics (holdings, totals, `totalsUnavailable`, `derived`, `readFrom`), failure behavior, units, authentication, and data verification status. An agent has enough to invoke the tool and interpret its result correctly.

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 has zero parameters and the input schema is empty, so there is no parameter-semantics burden for the description to carry. The baseline of 4 applies; the description instead adds useful context about output fields and failure behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the tool as returning the user's actual stock holdings at Stockbit Sekuritas, including average price and current value. It explicitly distinguishes itself from `watchlist` as account vs. list, eliminating ambiguity among siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-to-use guidance: read before any opinion touching position sizing, concentration, or adding to a position. It also names `watchlist` as the alternative and explains why it is not the same, satisfying the when/not/alternative expectation.

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