Skip to main content
Glama
Sign In
Portfolio Analytics MCP

Portfolio Analytics MCP

by RugSec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_etf_listings

Read-only

Retrieve every exchange where an ETF trades, including currency and ticker codes, to identify the right listing for a specific market such as XETRA or London.

Instructions

Exchanges where an ETF trades: currency, ticker, Bloomberg/Reuters codes.

    Useful to find the ticker for a specific exchange (e.g. XETRA vs London).

    Args:
        isin: ETF ISIN.
        refresh: Bypass the 24h cache.

    Returns:
        `listings`, one per exchange; or an `error`.

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": {
      "isin": "<isin>"
    },
    "name": "get_etf_listings"
  }
}

Input Schema

NameRequiredDescriptionDefault
isinYes
refreshNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description does not need to establish basic safety. It adds useful behavioral context by disclosing the 24-hour cache and the refresh flag that bypasses it, as well as noting that an error may be returned.

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 description is compact, front-loaded with the resource and purpose, and structured with clear Args and Returns sections. Every sentence adds useful information without repetition.

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 simple two-parameter lookup with no output schema, the description covers purpose, both arguments, caching behavior, and the return shape at a high level. It does not detail the exact listing object fields beyond the opening sentence, but it is sufficient for correct invocation.

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 compensate, and it does document both parameters: isin as the ETF ISIN and refresh as the cache-bypass flag. It does not specify ISIN formatting or validation, but both parameters are meaningfully explained.

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 clearly states the resource and output fields: exchange listings for an ETF, including currency, ticker, and Bloomberg/Reuters codes. It also gives a concrete use case, finding a ticker for a specific exchange, but does not explicitly differentiate itself from siblings such as get_symbol_info or resolve_instrument.

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

Usage Guidelines4/5

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

It provides a clear usage context: finding the ticker for a specific exchange such as XETRA versus London. It lacks explicit when-not-to-use guidance or named alternatives, but the intended scenario is easy to infer.

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

Deploy Server

Other Tools