Skip to main content
Glama

Fund fee cost

fund_fee_cost
Read-onlyIdempotent

Computes the weighted expense ratio of a list of holdings from dated issuer fee records, and the fee cost over 10 and 30 years on a flat $100,000 balance (before growth), using the same formula as the Portfolio Optimizer Pro expense ratio calculator. Single companies count as 0% fund fee. If any fund fee is not verified the weighted fee is null and the ticker is listed, rather than estimated.

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

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
formulaYes
noticesYes
holdingsYes
disclaimerYes
unknown_tickersYes
unverified_tickersYes
fee_cost_10y_on_100k_usdYes
fee_cost_30y_on_100k_usdYes
weighted_expense_ratio_pctYesNull when any fund fee is not verified.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent/closed-world annotations by disclosing the calculation basis ('flat $100,000 balance, before growth'), the treatment of single companies (0% fund fee), and an explicit failure mode: unverified fees yield a null weighted fee with the offending ticker named instead of an estimate. That failure-mode contract is exactly what an agent needs before acting on the result.

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 tight sentences, front-loaded with the computation and its outputs, followed by edge-case rules. The 'Portfolio Optimizer Pro' product reference is the only borderline filler, though it does serve to pin the formula to a reproducible source.

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 a single required parameter, full schema coverage, and an output schema covering return values, the description supplies everything else an agent needs: the formula's basis, edge-case handling for company-only portfolios, and null-vs-estimate behavior. Nothing material to calling 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 coverage is 100%, so the baseline is 3, and the description adds genuinely new meaning about the ticker dimension ('single companies count as 0% fund fee') and about how holdings are aggregated into a weighted ratio. It stops short of clarifying weight normalization or duplicate-ticker handling in prose, leaving those to the schema.

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?

States a specific verb ('Computes') with two concrete outputs (weighted expense ratio and fee cost over 10/30 years) from defined inputs (dated issuer fee records). An agent knows exactly what it receives and can distinguish it from grading or overlap-checking siblings.

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 by the input shape (a weighted holdings list), so it is clear this is the fee-analysis call for a portfolio, but there is no explicit 'use this when...' trigger, no stated prerequisites (e.g. that fees must be verified), and no referenced alternative among check_overlap, explain_grading, or grade_portfolio.

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