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

T-Bank Invest MCP Server (read-only)

by Sicness

get_etf_by

Read-only

Retrieve detailed ETF or fund data—including management fee, tracking index, and rebalance frequency—by ticker, FIGI, ISIN, or UID.

Instructions

Get detailed ETF/fund info: management fee, tracking index, rebalance frequency.

Args: id: ETF ticker, FIGI, ISIN or UID — which one it is gets recognised automatically id_type: Only needed with class_code: INSTRUMENT_ID_TYPE_TICKER. Otherwise leave the default. class_code: Board of a ticker (e.g. "TQBR"), to pick one listing out of several

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": {
      "id": "<id>"
    },
    "name": "get_etf_by"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
id_typeNoINSTRUMENT_ID_TYPE_FIGI
class_codeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/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. The description adds the returned field set, which is useful since no output schema exists, but says nothing about failure behavior for an unknown id, rate limits, or whether funds other than ETFs are covered.

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 one-line purpose followed by a short Args block; no filler sentences. It is slightly longer than strictly necessary because the schema already carries the enum and defaults, but the added param explanation earns its place given 0% schema coverage.

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?

For a read-only single-instrument lookup with no output schema, the description covers purpose, return fields, and all three parameters adequately. The remaining gaps (not-found behavior, ETF vs fund scope, identifier precedence conflicts) are modest.

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 burden and largely meets it: it explains that id accepts ticker/FIGI/ISIN/UID with automatic recognition, that id_type is only needed for ticker lookups, and that class_code selects a board (e.g. "TQBR"). The id_type sentence is awkwardly worded ('Only needed with class_code: INSTRUMENT_ID_TYPE_TICKER'), which slightly muddies the actual constraint, but all three params get meaningful context.

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 states a specific verb and resource ('Get detailed ETF/fund info') and enumerates the fields returned (management fee, tracking index, rebalance frequency). It is distinguishable from get_share_by/get_bond_by by resource, though it does not explicitly contrast itself with list_etfs or get_instrument_by.

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?

Usage is implied: the tool is for looking up a single ETF by an identifier, and the id/id_type/class_code notes hint at how to disambiguate a listing. However, there is no explicit when-to-use-this-vs-alternatives guidance, e.g. vs list_etfs for enumeration or find_instrument for search.

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