Skip to main content
Glama

Portfolio Terminal

How much two ETFs overlap

etf_overlap
Read-onlyIdempotent

How much of two ETFs is the same money: overlap by weight (the sum, over companies both hold, of the smaller of the two weights), how many companies they share, what share of each fund sits in names the other also holds, and the largest shared holdings. Full issuer files, matched on ISIN. Use it for "VOO vs QQQ overlap", "is IVV the same as VOO".

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": {
      "fund_a": "<fund_a>",
      "fund_b": "<fund_b>"
    },
    "name": "etf_overlap"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many shared holdings to return (1–50, default 10).
fund_aYesFirst fund ticker, e.g. "VOO", or "IQQY.DE" for a UCITS fund.
fund_bYesSecond fund ticker, e.g. "QQQ".

Output Schema

NameRequiredDescriptionDefault
aYes
bYes
urlYes
aInBYes
asOfYes
bInAYes
onlyAYes
onlyBYes
sharedYes
overlapYes
verdictYes
sharedCountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / fund_a / description
      Previous value: -"First fund ticker, e.g. \"VOO\"."New value: +"First fund ticker, e.g. \"VOO\", or \"IQQY.DE\" for a UCITS fund."
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds genuinely useful context beyond that: the data source is 'full issuer files, matched on ISIN', which tells the agent how funds are reconciled (cross-listings/UCITS tickers work). It says nothing about coverage gaps, unknown-ticker behavior, or cost of the call.

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 the core metric and its exact formula, which is the right ordering for an agent deciding whether to call it. The long parenthetical is dense but each clause defines a distinct reported number; the closing example sentence is the only part that could be trimmed.

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?

For a three-parameter read-only tool with a full output schema, the definition covers what is computed, how funds are matched, and when to reach for it. Return-value detail is correctly delegated to the output schema, leaving no material gap for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and both required tickers plus the limit are fully documented in the schema, so baseline is 3. The description adds essentially nothing parameter-specific beyond restating 'largest shared holdings' as what limit controls, and it never clarifies that fund order is irrelevant or how limit interacts with the reported share percentages.

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?

Names a specific computation on a specific resource: overlap by weight defined as 'the sum, over companies both hold, of the smaller of the two weights'. It also enumerates the three other outputs (shared company count, share of each fund in overlapping names, largest shared holdings), which no sibling tool (etf_holdings, who_holds, compare) provides in this pairwise form.

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?

Example phrasings ('VOO vs QQQ overlap', 'is IVV the same as VOO') give concrete situations that should route to this tool rather than etf_holdings or who_holds. It does not explicitly state when not to use it, e.g. that single-fund inspection should go to etf_holdings, so it stops short of full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources