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

T-Bank Invest MCP Server (read-only)

by Sicness

get_trading_status

Read-only

Check whether an instrument is currently tradeable or in an auction phase using its ticker, FIGI, ISIN, or UID.

Instructions

Get current trading status for an instrument: is it tradeable, auction phase, etc.

Args: instrument_id: Instrument ticker, FIGI, ISIN or UID

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_id": "<instrument_id>"
    },
    "name": "get_trading_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
instrument_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered and the description's job is lighter. It does add that the response reflects 'current' status and includes fields like tradeable and auction phase, which is useful context. It stops short of saying anything about freshness/latency, exchange session dependency, or failure behavior for invalid instruments.

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 purpose in the first clause, followed by a compact illustration of the payload. The 'Args:' block is slightly boilerplate for a one-parameter tool but costs little. No wasted sentences.

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

Completeness3/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 is the only place return values can be explained, and it gives only a partial sketch ('tradeable, auction phase, etc'). The 'etc' leaves the actual shape unknown. For a simple read-only, single-parameter status tool this is minimally viable, but it under-delivers on the return contract.

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 for the single parameter, and it does so well by naming the four accepted identifier formats (ticker, FIGI, ISIN, UID). That is exactly the kind of syntax information the bare schema lacks. It doesn't state whether formats can be mixed or which is preferred.

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 current trading status for an instrument') and enumerates the payload ('is it tradeable, auction phase, etc'), which lets an agent distinguish it from list/lookup siblings. It does not, however, differentiate itself from the adjacent get_trading_schedules tool, so the boundary between the two remains ambiguous.

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 guidance. The closest sibling, get_trading_schedules, is never mentioned, and the agent is left to infer whether this returns a live flag or a calendar. Nothing tells the caller what happens if the instrument is halted or unknown.

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