Skip to main content
Glama
Sign In
Portfolio Analytics MCP

Portfolio Analytics MCP

by RugSec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_similar_etfs

Read-only

Find ETFs tracking the same index to compare costs and size. Use this to check if a cheaper alternative exists for a given ISIN.

Instructions

ETFs on the same index (justETF's "further ETFs") with size, TER, policy.

    Good for "is there a cheaper ETF tracking the same index?".

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

    Returns:
        The index, this ETF's TER and size, and `similar_etfs`; 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_similar_etfs"
  }
}

Input Schema

NameRequiredDescriptionDefault
isinYes
refreshNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnlyHint and openWorldHint, and the description adds genuinely new behavioral facts: results are cached for 24h and the `refresh` flag bypasses that cache, plus it names the returned fields and the error path. The only gap is that it doesn't say how large the similar list can be or whether it can be empty.

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?

The content is front-loaded: what it returns comes first, then the use case, then Args and Returns. It is appropriately short for a two-parameter read tool, with only slight redundancy between the opening line and the Returns block.

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 read-only, two-parameter tool with no output schema, the description covers purpose, inputs, caching behavior, and the shape of the return value including the error case. Nothing essential to invoking it correctly is missing.

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 carries the burden, and it does document both parameters in the Args block. 'ETF ISIN' is minimal, but 'Bypass the 24h cache' gives real semantic meaning to `refresh` that the bare boolean schema does not convey.

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 states a specific resource and scope: ETFs tracking the same index, drawn from justETF's 'further ETFs', returned with size, TER and policy. That is concrete enough to separate it from search_etf or get_etf_profile, though it never explicitly contrasts itself with compare_etfs, which is the closest sibling.

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?

The line 'Good for "is there a cheaper ETF tracking the same index?"' gives a clear situational trigger that maps directly to the tool's purpose. It is missing any explicit exclusion or pointer to alternatives (e.g. use compare_etfs for a side-by-side of chosen ISINs), so usage is clear but not fully disambiguated.

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