Skip to main content
Glama
Batonec

tinkoff-wealth-mcp

by Batonec

investor_get_portfolio

Retrieve your current aggregated investment portfolio, including holdings, allocation breakdown, and detailed positions.

Instructions

Return current aggregated portfolio.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idsNo
refreshNo
include_positionsNo
include_allocationNo
Behavior3/5

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

No annotations are provided, so the description carries the burden of behavioral disclosure. 'Return current aggregated portfolio' suggests a read operation with no side effects, but it fails to mention that the 'refresh' parameter may trigger a data fetch. This is a moderate gap given the lack of annotations.

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?

The description is a single, clear sentence with no superfluous words. It is front-loaded and efficient.

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

Completeness2/5

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

Given the tool has 4 parameters with no output schema, the description should provide more context on return structure and parameter effects. 'Aggregated portfolio' is vague; it does not specify the format or what aggregation means. This is insufficient for an agent to correctly invoke and interpret results.

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?

With 0% schema description coverage, the description should compensate by explaining parameters. It does not mention account_ids, refresh, include_positions, or include_allocation. The parameter names are somewhat self-explanatory, but the meaning of 'refresh' (e.g., force a remote fetch) and the default behaviors are not clarified.

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 'Return current aggregated portfolio' clearly states the verb (Return) and resource (aggregated portfolio). However, it does not differentiate from sibling tools like investor_analyze_portfolio or investor_get_profile, missing an opportunity to clarify its specific role.

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?

No usage guidance is provided. The description does not indicate when to use this tool versus alternatives such as investor_analyze_portfolio or investor_explain_portfolio_change, leaving the agent to infer based on name alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Batonec/Tinkoff-wealth-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server