Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Stock allocation

account_allocation
Read-onlyIdempotent

Retrieves how your portfolio is distributed across individual stocks and sectors, showing allocation in IDR based on 100-share lots for trading-session accounts.

Instructions

How the portfolio is spread across stocks and sectors.

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

Returns (Stockbit's data field): {data:...}

Endpoint: GET carina /history/performance/portfolio/stock-allocation.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 readOnly, idempotent, non-destructive, and open-world behavior, so the safety profile is covered. The description adds real context beyond them: a required trading session, IDR units, and share lots of 100, but it says nothing about freshness, caching, or failure modes for an authenticated endpoint.

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?

Four short lines, front-loaded with the meaning of the data, then prerequisites, then units, then return shape. Every line carries information for the caller and nothing is padded.

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 zero-parameter read with no output schema, the description covers the prerequisite, the semantics of the values, and the general shape of the response ({data:...}). It is close to complete, with the only gap being the exact fields returned, which the loose return note does not enumerate.

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 the baseline is 4 and the schema has nothing to explain. The description still adds interpretation value by fixing units (IDR) and lot size (100 shares), which affects how an agent reads the result.

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 states the specific resource clearly: how the portfolio is spread across stocks and sectors, which an agent can distinguish from a portfolio-holdings-shaped tool at a glance. It stops short of naming which sibling (e.g. account_portfolio_summary or account_position) it differs from, so sibling differentiation is left implicit.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no named alternatives among the many account_* siblings. The only situational information is a precondition (a trading-session login is required), which is a prerequisite rather than guidance on choosing this tool.

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