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

T-Bank Invest MCP Server (read-only)

by Sicness

get_last_prices

Read-only

Fetch last trade prices for one or more instruments by ticker, FIGI, ISIN, or UID; each result includes ticker and classCode, with an error for unmatched IDs. Bond prices are percent of nominal.

Instructions

Get last trade prices for one or more instruments.

One record per requested identifier, in the order of the request, each with its ticker and classCode. An identifier no instrument matches gives {"requested": ..., "error": ...} in its place. A bond's price is in percent of its nominal, not in money.

Args: instrument_ids: Comma-separated list of tickers, FIGIs, ISINs or UIDs

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": {
      "instrument_ids": "<instrument_ids>"
    },
    "name": "get_last_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
instrument_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds meaningful behavior beyond them: one record per requested identifier in request order, each carrying ticker and classCode, an inline error object for unmatched identifiers, and the bond pricing convention (percent of nominal, not money). These are non-obvious runtime traits that an agent could not derive from the annotations.

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 purpose, then structured expansion for return shape, error handling, and the domain-specific bond caveat; the Args block adds the parameter detail. Every sentence carries information, with only minor redundancy in restating the argument name.

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

Completeness4/5

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

With no output schema, the description takes on return-shape disclosure and does it: record-per-identifier, ordering, field contents, and error placeholders. The main residual gap is pricing semantics for non-bond instruments (which price is used, staleness/currency), plus no note on batching limits.

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 0% and the schema only labels the field 'Instrument Ids', so the description carries the burden and does so well by enumerating the acceptable identifier forms (tickers, FIGIs, ISINs, UIDs) and the comma-separated format. It stops short of delimiter/escaping edge cases, but it substantially compensates for the empty schema.

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 last trade prices') plus the scope ('for one or more instruments'), which is clear enough for an agent to distinguish from list/find siblings. However, it never contrasts itself with the obviously adjacent sibling get_close_prices, so sibling differentiation is left to inference.

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?

There is no when-to-use, when-not-to-use, or alternative-tool guidance at all. The closest sibling, get_close_prices, is never mentioned, and no condition is given for choosing last trade price versus close price or candle data.

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