Skip to main content
Glama

Fintel Discovery — Financial Intelligence for AI Agents

Get Fund Expense Ratios — XBRL rr: Taxonomy

GetFundFees
Read-onlyIdempotent
    Retrieve expense ratios and fee breakdown for a mutual fund or ETF using
    its SEC CIK. Reads structured XBRL data filed with prospectuses using the
    SEC Risk/Return (rr:) taxonomy. Returns:
      - net_expense_ratio    — total annual cost to the investor (%)
      - gross_expense_ratio  — before waivers/reimbursements (%)
      - management_fee       — advisor/sub-advisor fee (%)
      - distribution_12b1_fee — distribution and service fee (%)
      - other_expenses       — admin, custody, transfer agent fees (%)
      - acquired_fund_fees   — fees from underlying funds, if any (%)

    All values are expressed as percentages (e.g. 0.03 = 0.03%).

    PRIMARY USE: Step 2 of fee comparison. Accepts CIKs returned by
    SearchFundsByCategory. Run for multiple funds then rank by net_expense_ratio
    ascending to find the lowest-cost option in a category.

    With include_all_classes=True (default), returns one row per share class
    per period — useful for identifying the cheapest share class of a fund.
    With include_all_classes=False, returns the single most recent value only.

    Note: Not all funds file XBRL rr: data. If this tool returns an error,
    use GetFundProfile (yfinance) as a fallback for expense ratio data.

    Source: SEC EDGAR XBRL company facts API. No API key required.
    

Input Schema

NameRequiredDescriptionDefault
paramsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $defs / FundFeesParams / properties / mcp_prompt_id / default
      Previous value: -"498d9131-d794-4dd2-b1d6-b4d19d83cf35"New value: +"1e3db2ac-608d-4ff7-8b19-8fc78826e993"
  2. Changed1 schema field changed
    • changedInput schema / $defs / FundFeesParams / properties / mcp_prompt_id / default
      Previous value: -"05525087-35e9-4aac-b06d-6d88ce386b2e"New value: +"498d9131-d794-4dd2-b1d6-b4d19d83cf35"
  3. Changed1 schema field changed
    • changedInput schema / $defs / FundFeesParams / properties / mcp_prompt_id / default
      Previous value: -"f258bd16-f060-4e4a-a55d-221a0484866d"New value: +"05525087-35e9-4aac-b06d-6d88ce386b2e"
  4. Changed1 schema field changed
    • changedInput schema / $defs / FundFeesParams / properties / mcp_prompt_id / default
      Previous value: -"5f4db44b-e5cc-4f3a-8da3-ac591a019c81"New value: +"f258bd16-f060-4e4a-a55d-221a0484866d"
  5. Changed1 schema field changed
    • changedInput schema / $defs / FundFeesParams / properties / mcp_prompt_id / default
      Previous value: -"d9f77642-e017-4785-9150-e658c2dba3a0"New value: +"5f4db44b-e5cc-4f3a-8da3-ac591a019c81"
  6. Changed1 schema field changed
    • changedInput schema / $defs / FundFeesParams / properties / mcp_prompt_id / default
      Previous value: -"dbe99169-c071-4ed4-9ae9-8bbfb9a88ad8"New value: +"d9f77642-e017-4785-9150-e658c2dba3a0"
  7. Changed1 schema field changed
    • changedInput schema / $defs / FundFeesParams / properties / mcp_prompt_id / default
      Previous value: -"3775b46a-5aa8-4586-af57-2453c8bcd08c"New value: +"dbe99169-c071-4ed4-9ae9-8bbfb9a88ad8"
  8. Changed1 schema field changed
    • changedInput schema / $defs / FundFeesParams / properties / mcp_prompt_id / default
      Previous value: -"d81a5175-11e9-494a-baa5-71d4ffad4ab9"New value: +"3775b46a-5aa8-4586-af57-2453c8bcd08c"
  9. Changed1 schema field changed
    • changedInput schema / $defs / FundFeesParams / properties / mcp_prompt_id / default
      Previous value: -"9e7f8798-7d22-4378-b93d-179c6f8cb854"New value: +"d81a5175-11e9-494a-baa5-71d4ffad4ab9"
  10. Changed1 schema field changed
    • changedInput schema / $defs / FundFeesParams / properties / mcp_prompt_id / default
      Previous value: -"9919ff85-e960-472f-863b-3de4c5abed9f"New value: +"9e7f8798-7d22-4378-b93d-179c6f8cb854"
  11. Changed1 schema field changed
    • changedInput schema / $defs / FundFeesParams / properties / mcp_prompt_id / default
      Previous value: -"38452924-d5df-4668-b51c-d7cd5acabc09"New value: +"9919ff85-e960-472f-863b-3de4c5abed9f"
  12. Changed1 schema field changed
    • changedInput schema / $defs / FundFeesParams / properties / mcp_prompt_id / default
      Previous value: -"fa72f604-6239-428b-81df-11f07c2c8d00"New value: +"38452924-d5df-4668-b51c-d7cd5acabc09"
  13. Changed1 schema field changed
    • changedInput schema / $defs / FundFeesParams / properties / mcp_prompt_id / default
      Previous value: -"7b866f24-13ab-4e54-8d3a-f775612c393f"New value: +"fa72f604-6239-428b-81df-11f07c2c8d00"
  14. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent, and the description adds substantive context beyond them: the SEC EDGAR source, no API key required, the error condition for funds that don't file rr: data, and the include_all_classes row-granularity tradeoff. It does not discuss pagination or how many funds can be batched, which is the remaining gap.

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 purpose, then a compact bullet breakdown, then workflow guidance — easy to scan. The enumeration of return fields is largely redundant given an output schema exists, costing some space.

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, single-resource retrieval tool with an output schema, the description covers source, prerequisites (CIK), failure mode and fallback. The redundancy of restating output fields is the main weakness rather than a missing critical detail.

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?

Cik semantics are reinforced (zero-padding handled automatically, example CIK) and include_all_classes is explained behaviorally in both description and schema. The description does not touch the many auxiliary params the schema carries (wholesaler_ids, source_resource_id, exclude_fillers), but those have rich schema text of their own.

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+resource ('retrieve expense ratios and fee breakdown for a mutual fund or ETF') and names the exact data source (SEC EDGAR XBRL rr: taxonomy via CIK). It clearly separates itself from siblings by naming GetFundProfile as the fallback and SearchFundsByCategory as the CIK supplier.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit workflow placement ('Step 2 of fee comparison'), tells the agent to run it across multiple CIKs and rank by net_expense_ratio ascending, and names an alternative (GetFundProfile) for the case where XBRL data is missing. When/when-not/alternative routing is all present.

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