Skip to main content
Glama

Get my portfolio positions

acubic_get_portfolio
Read-onlyIdempotent

Returns holdings, value, return since activation and the last rebalance outcome of the person's live or paper-money strategies, from Acubic's latest daily snapshot (as_of); it does not contact the broker and never returns credentials or account numbers. Use it for how a running portfolio is doing; to start automating use acubic_go_live.

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": "acubic_get_portfolio"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPage size.
cursorNoA previous next_cursor.
localeNoThe language of this conversation.
strategy_idNoOne strategy; omit for all that have a live or paper book.
response_formatNoconcise

Output Schema

NameRequiredDescriptionDefault
errorNo
truncatedNo
disclosureNo
portfoliosNo
next_cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the description adds genuinely new behavior: results come from a daily snapshot rather than live data, no broker is contacted, and credentials/account numbers are never returned. That freshness and data-exposure context materially changes how an agent should trust and present the numbers. Pagination behavior beyond the schema's limit/cursor is not described, which is why it is not 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?

Two sentences, no filler, with the resource and data-freshness constraint front-loaded and the sibling routing at the end. The first sentence is long and list-heavy but every clause carries information; a slightly tighter structure would read faster.

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?

An output schema exists, so return values need not be described. Combined with the freshness disclosure, the no-broker/no-credentials guarantees, the strategy scoping, and the explicit alternative, an agent has everything needed to call this correctly and interpret its results.

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?

Schema description coverage is 80%, so the baseline is 3; the description lifts it slightly by pinning the concept of 'as_of' and clarifying that results span 'live or paper-money strategies', reinforcing what strategy_id selects and what omitting it means. It adds nothing for locale, response_format, limit or cursor, but those are already documented in the schema.

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 opens with a specific verb and resource ('Returns holdings, value, return since activation and the last rebalance outcome') scoped to 'live or paper-money strategies', and it names the exact data source ('Acubic's latest daily snapshot (as_of)'). It explicitly contrasts itself with acubic_go_live, so an agent can distinguish it from the sibling without opening either schema.

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

Usage Guidelines4/5

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

'Use it for how a running portfolio is doing; to start automating use acubic_go_live' gives a clear positive condition plus a named alternative with its own selection condition. There is no explicit when-not guidance relative to other read siblings such as acubic_get_strategy or acubic_list_strategies, which keeps it just short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources