Skip to main content
Glama
Portfolio Analytics MCP

Portfolio Analytics MCP

by RugSec

search_etf

Read-only

Find an ETF's ISIN from a name, ticker, index, or ISIN; use this first because other justETF tools require the ISIN.

Instructions

Find an ETF's ISIN from its name, ticker or index (use this first).

    Accepts e.g. "iShares Core MSCI World", "IWDA", "vanguard all world acc"
    or an ISIN. Returns matches with ISIN, name and tickers. Yahoo Finance is
    used as a fallback for fuzzy names; hits that cannot be mapped to an ISIN
    come back in `unresolved_candidates` (isin null). Accumulating vs
    distributing and hedged variants look alike: if several matches are
    plausible, ASK THE USER which one they hold. All other justETF tools
    need the ISIN.

    Args:
        query: Fund name, ticker, index name or ISIN.
        max_results: Maximum matches to return.
        use_yahoo: Also query Yahoo Finance when the registry has no full match.

    Returns:
        `matches` with ISIN, name, tickers and match type; optional
        `unresolved_candidates`; a `note` on what to do next.
    

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": {
      "query": "<query>"
    },
    "name": "search_etf"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
use_yahooNo
max_resultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnly and openWorld annotations, it discloses the Yahoo Finance fallback for fuzzy names, that unmapped hits appear in unresolved_candidates with null ISIN, and that ambiguous share-class matches require user clarification. This is rich behavioral context for a search tool.

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 front-loaded with the primary action and routing advice, then uses short sections for examples, caveats, Args, and Returns. The length is justified by the ambiguity handling and lack of an output schema.

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?

Although there is no output schema, the description explains the return shape: matches, optional unresolved_candidates, and a note. Combined with parameter explanations and ambiguity guidance, it gives the agent everything needed to call and interpret the tool.

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 parameter meaning. It explains query as a fund name, ticker, index name, or ISIN, and use_yahoo as a fallback trigger, but max_results is only restated as 'Maximum matches to return' without constraints or default guidance.

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?

The description states a specific verb and resource: find an ETF's ISIN from name, ticker, index, or ISIN. It positions the tool as the first step before other justETF tools, which makes its role distinct from downstream profile/holdings/performance tools.

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?

It explicitly says to use this first and explains that all other justETF tools need the ISIN. It also gives concrete query examples and instructs the agent to ask the user when accumulating, distributing, or hedged variants are plausible.

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