Skip to main content
Glama
Sign In
Portfolio Analytics MCP

Portfolio Analytics MCP

by RugSec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_etf_profile

Read-only

Retrieve key ETF facts like TER, fund size, and distribution policy using an ISIN to evaluate or compare exchange-traded funds.

Instructions

Key facts about an ETF from justETF, looked up by ISIN.

    Example ISIN: IE00B4L5Y983 (iShares Core MSCI World, Acc).

    Args:
        isin: ETF ISIN (12 characters).
        refresh: Bypass the 24h cache and re-download the page.

    Returns:
        Name, ticker, TER (% p.a.), fund size, distribution policy
        (accumulating/distributing), replication, index, fund currency and
        currency hedging, domicile, provider, inception date, number of
        holdings, legal structure, tax status per country, securities
        lending and a description; 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_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
isinYes
refreshNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/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 useful behavioral context beyond annotations: a 24h cache exists and refresh bypasses it, and the response includes a full field list or an `error`. It stops short of discussing rate limits or scraping failures in detail.

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 with purpose, then example, args, and returns in a clean structure. The return field list is long but earns its place because there is no output schema; the prose is otherwise economical.

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?

Given no output schema, the description appropriately enumerates return fields and the error case. Combined with the cache/refresh note and ISIN format, an agent has enough to call this correctly; only minor operational details like rate limiting or refresh cost are absent.

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 load, and it does: `isin` is defined as a 12-character ETF ISIN with a concrete example, and `refresh` is explained as bypassing the 24h cache. It could note the default false for refresh, but otherwise the parameters are well covered.

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?

States a specific verb and resource: key facts about an ETF looked up by ISIN from justETF. Clear and concrete, but it does not explicitly differentiate itself from siblings like get_symbol_info or search_etf beyond the ISIN-based lookup and justETF source.

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: look up an ETF profile when you have an ISIN. There is no explicit guidance about when not to use it (e.g., use search_etf to discover an ISIN first, or use get_etf_holdings for holdings).

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