Skip to main content
Glama
Batonec

tinkoff-wealth-mcp

by Batonec

investor_explain_portfolio_change

Explain changes in your investment portfolio over a specified date range or period, with optional account selection and news context.

Instructions

Explain portfolio change for a period. Date range uses from_date/to_date.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
periodNoweek
from_dateNo
to_dateNo
account_idsNo
include_newsNo
Behavior2/5

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

No annotations are provided, so the description must carry full burden. It states 'explain' but does not describe what the explanation entails (e.g., narrative, summary, data). Critical behavioral traits like destructive potential or response format are omitted.

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?

Two concise sentences with no fluff. The key action and date range are front-loaded.

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 5 parameters, no output schema, and no annotations, the description is too brief. It does not specify output format, whether the tool is read-only, or how the explanation is structured. Lacks completeness for practical use.

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?

Schema description coverage is 0%. Description only mentions 'from_date/to_date', leaving 'period', 'account_ids', and 'include_news' unexplained. It adds minimal meaning beyond the schema, failing to compensate for the lack of parameter descriptions.

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 clearly states 'Explain portfolio change for a period', specifying the verb 'explain' and resource 'portfolio change'. It implicitly distinguishes from sibling tools like 'investor_get_portfolio' (returns current state) and 'investor_analyze_portfolio' (likely does analysis), but does not explicitly contrast.

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 provides context for when to use (for a period), but gives no guidance on when not to use or how it compares to siblings like 'investor_analyze_portfolio'. No alternatives or exclusions are mentioned.

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