Skip to main content
Glama
T-Bank Invest MCP Server (read-only)

T-Bank Invest MCP Server (read-only)

by Sicness

get_portfolio

Read-only

Fetch a T-Bank Invest account's full holdings: total values by asset type, positions, quantities, current prices, and yields by account ID and currency.

Instructions

Get full portfolio for an account: total values by asset type, all positions with prices, yields, and quantities.

Each position has ticker, classCode, figi, instrumentUid, positionUid, instrumentType, quantity, averagePositionPrice, currentPrice, expectedYield, dailyYield, currentNkd (bonds) and its currency. Amounts are plain numbers; a field that is zero or false is left out, and so are the two fields the API has deprecated.

expectedYield and dailyYield of a position are amounts of money in the position's currency, not percentages; the portfolio's own expectedYield, at the top level, is a percentage. A bond's averagePositionPrice and currentPrice are money per bond, and currentNkd is the accrued interest per bond in the same currency — while get_last_prices, get_candles and get_order_book give a bond's price in percent of its nominal. positionUid is the key of a position: one paper can come under several figi and instrumentUid (its listings), all with the same positionUid.

Args: account_id: Account ID (get from get_accounts) currency: Portfolio currency — RUB, USD, or EUR (default: RUB)

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": {
      "account_id": "<account_id>"
    },
    "name": "get_portfolio"
  }
}

Input Schema

NameRequiredDescriptionDefault
currencyNoRUB
account_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses genuinely useful behavior: zero/false fields are omitted, deprecated fields are dropped, expectedYield/dailyYield are money rather than percentages (but the portfolio-level one is a percentage), bond averagePositionPrice/currentPrice are per-bond money, and positionUid is the true position key. This is exactly the extra context annotations cannot carry.

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?

Fairly long but information-dense and front-loaded: purpose first, then field enumeration, then unit/semantics caveats, then args. Given there is no output schema, the field-level detail earns its place; only marginal redundancy remains.

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?

With no output schema and zero parameter descriptions, the description compensates by describing the return shape, field meanings, unit conventions, position keying, and where to source account_id. It is complete enough for an agent to call and interpret the result correctly.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must carry the load. It adds real value for account_id ('get from get_accounts'), but for currency it only restates the enum values and default already present in the schema, leaving the gap only partly closed.

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 verb and resource ('Get full portfolio for an account') and enumerates the payload (totals by asset type, all positions with prices, yields, quantities), so the agent knows exactly what it gets. It does not explicitly contrast its scope with the sibling get_positions, so it stops short of full sibling differentiation.

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?

There is no explicit when-to-use/when-not statement, but it does route the agent to the prerequisite tool ('account_id ... get from get_accounts') and clarifies how its bond price units differ from get_last_prices, get_candles and get_order_book. That is implied usage rather than a stated selection rule.

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