Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Cumulative return vs IHSG

account_performance_cumulative
Read-onlyIdempotent

Track your portfolio's cumulative return over time to compare it against a benchmark index. Requires a trading session and a time filter.

Instructions

Cumulative return of the portfolio over time, to compare with the index.

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

Returns (Stockbit's data field): {data:{portfolio_returns:[{date, percentage}]}}

Endpoint: GET carina /history/performance/portfolio/cumulative-return.

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": {
      "time_filter": "<time_filter>"
    },
    "name": "account_performance_cumulative"
  }
}

Input Schema

NameRequiredDescriptionDefault
time_filterYestime_filter

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is covered. The description adds genuinely useful disclosure beyond that: the auth/session requirement, that values are IDR, the literal response envelope ({data:{portfolio_returns:[{date, percentage}]}}), and the underlying endpoint. The 'lots of 100 shares' note is noise for a percentage series but does not undermine the rest.

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?

Purpose is front-loaded in the opening line, followed by terse, clearly delimited lines for prerequisite, units, return shape, and endpoint. The material is dense but every line is short; only the IDR/100-share line fails to earn its place in a tool that returns percentages.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description correctly fills the gap by spelling out the returned field structure, and it flags the auth requirement. However, for a tool with exactly one required parameter, the absence of any time_filter format guidance is a material incompleteness that will likely cause a failed first invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one required parameter, time_filter, and every description of it — both schema and prose — is the tautology 'time_filter'. Nothing states the accepted format (e.g. '1W', '1M', 'YTD') or whether it is a preset or a date range, so an agent must guess the single most important input. Schema coverage is nominally 100%, but that coverage carries zero semantic content, which justifies scoring below the baseline.

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 states a specific verb and resource: cumulative return of the portfolio over time compared against the index, and the title pins the benchmark as IHSG. It is clearly a time-series performance series, distinguishable in kind from account_performance_return or account_performance_equity, though it never says explicitly how it differs from those siblings.

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 description gives a real prerequisite ('Needs the trading session (stockbit-mcp login --trading)'), which is actionable context an agent would otherwise miss. It offers no when-to-use versus when-not-to-use guidance relative to the other account_performance_* tools, so selection between scoring/return/equity/cumulative series is left implicit.

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