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

T-Bank Invest MCP Server (read-only)

by Sicness

list_etfs

Read-only

Dump the complete ETF and fund reference list, including every field, for scripts. Choose tradeable or all instrument statuses; use find tools for single funds.

Instructions

Get the full reference list of ETFs and funds: every field of every fund.

A dump for scripts, not something to read: about 280 funds and 300 KB of JSON with INSTRUMENT_STATUS_BASE, 2.3 MB with INSTRUMENT_STATUS_ALL — more than fits in a model's context; a client saves such a result to a file or refuses it. To find particular funds use find_instrument with instrument_kind="etf", and get_etf_by for one.

Args: instrument_status: INSTRUMENT_STATUS_BASE (tradeable) or INSTRUMENT_STATUS_ALL

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_etfs"
  }
}

Input Schema

NameRequiredDescriptionDefault
instrument_statusNoINSTRUMENT_STATUS_BASE

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds the operational traits that matter — ~280 funds, ~300 KB vs 2.3 MB of JSON depending on status, exceeding typical model context, and that clients may save or refuse the result. That is real behavioral disclosure beyond the annotation layer.

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?

Two dense paragraphs: the payload warning is front-loaded right after the purpose statement, and the routing sentence follows. The size figures are specific and load-bearing rather than filler; no sentence is redundant.

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, the description supplies what the return looks like (all fields of all funds), how large it is under each parameter value, and how a client is likely to handle it. An agent has everything needed to decide whether to call this or a narrower sibling.

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 must carry the parameter meaning, and it does gloss INSTRUMENT_STATUS_BASE as the tradeable subset and contrasts it with ALL, including the size difference. It does not spell out what INSTRUMENT_STATUS_ALL includes beyond 'everything', so it stops short of full compensation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get the full reference list of ETFs and funds: every field of every fund') and immediately marks itself as a bulk dump rather than a lookup, which distinguishes it from get_etf_by and find_instrument without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly frames the use case ('A dump for scripts, not something to read') and routes the agent to alternatives with the exact parameter to supply: find_instrument with instrument_kind="etf" for finding funds, get_etf_by for a single fund. When-to-use and when-not-to-use are both stated.

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