Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Total equity history

account_performance_equity
Read-onlyIdempotent

Retrieve total account equity over time for a specified time filter to track portfolio value changes from Stockbit trading history; requires trading-session login.

Instructions

Total equity of the account over time.

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

Returns (Stockbit's data field): {data:{total:{amount}, equities:[...]}}

Endpoint: GET carina /history/performance/portfolio/total-equity.

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

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 readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds real context: the trading-session auth requirement, IDR currency, 'lots of 100 shares' unit convention, the response envelope shape, and the underlying endpoint. It does not mention pagination or how much history is returned, which is the main remaining behavioral gap.

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?

Front-loaded with the core statement, then prerequisite, units, return shape, and endpoint in short scannable lines. Slightly telegraphic ('Values IDR; lots of 100 shares') but every line carries information; nothing is padded.

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?

For a single-parameter read tool with no output schema, it covers auth, units, and return envelope, which is most of what is needed. The critical omission is the time_filter contract — an agent cannot construct a valid call without guessing the expected format — and history depth/pagination is unstated.

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 the schema's own description is just the literal string 'time_filter' — a tautology that conveys no format, granularity, or accepted values, and there is no enum. The tool description likewise says nothing about what time_filter accepts, so despite nominal 100% coverage the agent has no real semantics for the only input it must supply.

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 resource and scope: 'Total equity of the account over time.' An agent can tell this is a time-series equity read, distinct from return/cumulative/trades siblings by resource name. It stops short of explicitly contrasting with account_performance_cumulative or account_performance_return, which are the closest neighbors.

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?

Gives a concrete prerequisite ('Needs the trading session (stockbit-mcp login --trading)'), which is genuinely useful for deciding whether the call can succeed. However, it never says when to pick this over account_performance_cumulative or account_performance_return, so alternative selection is left to inference from names.

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