Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Bond portfolio

account_bonds
Read-onlyIdempotent

Retrieve the government bonds held in a Stockbit account, including ORI, SBR, and FR series with coupon details; requires a trading session.

Instructions

Government bonds held (ORI, SBR, FR …) with coupons.

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

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

Endpoint: GET carina /bond/v1/portfolio.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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, openWorld), and the description adds real context on top: an authentication prerequisite, currency and unit conventions (IDR, lots of 100 shares), and the response envelope shape. It does not describe pagination or behavior on an empty/unauthorized session, which keeps it below a 5.

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 the tool returns before the auth note and endpoint. The '{data:...}' and raw endpoint fragments are terse to the point of being cryptic but each line carries distinct information.

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 definition covers purpose, auth prerequisite, units, and the top-level return envelope. It omits the per-bond field set (quantity, coupon rate, maturity), which is the main remaining gap an agent would want before calling.

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 there is nothing for the description to disambiguate and the baseline is a 4. The unit note ('Values IDR; lots of 100 shares') adds interpretive meaning about how returned values should be read, which is a mild bonus.

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?

States a specific verb-resource pair ('Government bonds held') and enumerates example series (ORI, SBR, FR) with coupons, which clearly separates it from the equity-oriented account_portfolio sibling. It stops short of explicitly naming the alternative tool, so it is clear but not fully differentiated in-text.

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 rather than stated: an agent infers it should call this when it needs bond holdings rather than stock holdings. The prerequisite 'Needs the trading session (stockbit-mcp login --trading)' is a genuinely useful gating condition, but there are no explicit when-not cases or named alternatives.

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