Skip to main content
Glama
Sign In
Portfolio Analytics MCP

Portfolio Analytics MCP

by RugSec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

resolve_instrument

Read-only

Resolve an ISIN to Yahoo Finance tickers with best listing first, using exchange mappings and liquidity ranking for accurate market data retrieval.

Instructions

ISIN -> Yahoo Finance tickers, best listing first.

    Use this to go from an ISIN (broker statement, KID, justETF) to a
    symbol for the Yahoo tools. ETFs are mapped from their exchange
    listings on justETF (XETRA -> .DE, Euronext Amsterdam -> .AS, London
    -> .L, SIX -> .SW, ...); other ISINs (e.g. single stocks) fall back to
    Yahoo search. Listings in `base_currency` rank first, then the most
    liquid exchanges. Venues Yahoo lacks (gettex, Tradegate) are listed
    under `unmapped_listings`. If the user holds a specific listing,
    use that one.

    Args:
        isin: 12-character ISIN, e.g. IE00B4L5Y983.
        base_currency: Optional ISO code to prefer listings trading in it.

    Returns:
        `yahoo_candidates` best first, the `source` used and any
        `unmapped_listings`; or an error dict.

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": "resolve_instrument"
  }
}

Input Schema

NameRequiredDescriptionDefault
isinYes
base_currencyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly and openWorld, and the description adds real behavioral substance: the justETF-vs-Yahoo-search source split, the ranking heuristic (base_currency first, then liquidity), venue coverage (XETRA->.DE, etc.), and the existence of unmapped_listings. It does not mention rate limits or failure modes beyond 'an error dict', so a 4 rather than 5.

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?

Front-loads the one-line summary, then the usage rationale, then ranked behavior, then Args/Returns. Every sentence adds information (venue mapping, ranking rule, unmapped fallback) with no filler.

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 correctly documents the return shape (yahoo_candidates, source, unmapped_listings, error dict), which is exactly what an agent needs to consume the result. Nothing material is missing for a two-parameter resolver.

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 coverage is 0%, so the description must carry parameter meaning, and it does: isin is constrained to 12 characters with a concrete example, and base_currency is explained as an ISO code that prefers listings trading in that currency rather than just repeating the name. Both parameters are covered, so a strong score is warranted.

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?

Opens with a precise verb-and-resource mapping (ISIN -> Yahoo Finance tickers) plus ordering semantics ('best listing first'), which is distinct from search_symbol's symbol lookup. An agent can immediately tell what input it takes and what it produces.

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?

Gives concrete when-to-use context (ISIN from broker statement, KID, justETF) and the downstream purpose (symbol for the Yahoo tools). It also handles the ambiguity case ('If the user holds a specific listing, use that one'), though it never explicitly contrasts itself with the sibling search_symbol.

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