Skip to main content
Glama

Check fund overlap

check_overlap
Read-onlyIdempotent

Checks a list of holdings for known index overlap and related fund mandates, using issuer reference records (asset class, region, structure). Findings are worded exactly as the Portfolio Optimizer Pro grade states them. Overlap here is category-based (similar stated mandates); it is not a measured percentage of shared underlying holdings, and the result says so.

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": {
      "holdings": "<holdings>"
    },
    "name": "check_overlap"
  }
}

Input Schema

NameRequiredDescriptionDefault
holdingsYesThe portfolio: 1 to 30 holdings, each ticker once, with its weight.

Output Schema

NameRequiredDescriptionDefault
noticesYes
mandatesYes
disclaimerYes
method_noteYes
unknown_tickersYes
related_categoriesYes
known_index_overlapYesFund-overlap findings exactly as the grade states them; any one caps the grade.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already establish the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds substantive behavior beyond them: the reliance on issuer reference records (asset class, region, structure), the exact wording being inherited from the grade, and the explicit caveat that overlap is mandate-category-based rather than computed from shared underlying holdings. That is genuine added value.

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?

Three sentences, no padding, and the core purpose is front-loaded before the nuance. The final clause ('and the result says so') is slightly awkward and could be tightened, but the passage is efficient overall.

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?

An output schema exists, so the description needn't explain the return payload, and the tool's main ambiguity -- the meaning of 'overlap' -- is addressed explicitly. Combined with complete schema coverage and a clear read-only annotation profile, the definition is complete enough for correct invocation; only sibling-level routing guidance is missing.

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

Parameters3/5

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

Schema description coverage is 100%, so the ticker pattern, weight bounds, and normalization rules are already fully documented in the schema. The description restates the parameter as 'a list of holdings' without adding syntax or format detail, so it neither compensates for nor improves on the schema. Baseline 3 is appropriate.

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 opens with a specific verb and resource ('Checks a list of holdings for known index overlap and related fund mandates') and further narrows the scope with 'issuer reference records (asset class, region, structure)'. It does not name or contrast with the siblings (grade_portfolio, fund_fee_cost, explain_grading), though the purpose is articulated clearly enough to be distinguishable.

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 rather than stated: the agent learns the input shape (a portfolio of holdings) but not when to prefer this tool over grade_portfolio or fund_fee_cost. It does clarify what kind of question this tool answers ('category-based... not a measured percentage'), which implicitly scopes it, but no explicit when/when-not guidance or alternatives are offered.

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