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

T-Bank Invest MCP Server (read-only)

by Sicness

get_close_prices

Read-only

Fetch previous trading session closing prices for multiple instruments using tickers, FIGIs, ISINs, or UIDs, with one result per requested identifier.

Instructions

Get previous trading session close prices for instruments.

One record per requested identifier, in the order of the request. 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_close_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
instrument_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only cover readOnlyHint and openWorldHint, so the description adds real value: one record per identifier in request order, the exact error shape substitut ed for unmatched identifiers, and the non-obvious fact that bond prices are in percent of nominal rather than money. Missing only details such as how non-trading days are handled.

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 core behavior is front-loaded in the first sentence, followed by the output-contract detail and then the argument format. No sentence is filler and nothing important is buried.

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 steps in to describe the return structure and error records, and it documents the single required parameter. Only minor gaps remain, such as behavior on non-trading days or on an empty instrument list.

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%, so the description carries the full burden and does so well by listing the four accepted identifier forms (tickers, FIGIs, ISINs, UIDs) and the comma-separated format. It does not, however, show any example value or say whether mixed identifier types are permitted.

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 with scope: 'previous trading session close prices for instruments'. That is meaningfully narrower than siblings like get_last_prices or get_candles, though it never names those alternatives to sharpen the distinction.

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?

The description explains what the tool returns but never says when to use it over get_last_prices, get_candles, or get_stock_snapshot, nor does it state any prerequisites or exclusions. Usage must be inferred from the resource name alone.

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