Skip to main content
Glama

Edgar

by io.github.pipeworx-io
OverviewAdmin

Edgar Fund Holdings

edgar_fund_holdings
Read-onlyIdempotent

AUTHORITATIVE portfolio holdings of a US ETF or mutual fund (SEC Form N-PORT) — what the fund actually owns. Pass the FUND's ticker (e.g. "ARKK", "QQQ", "VTI", "VOO", "IVV"). Returns the latest monthly portfolio: net assets, holdings count, and top positions by weight — each with name, CUSIP, value (USD), and % of fund. Use for "what does ARKK hold", "top holdings of QQQ", "is $STOCK in VTI". Distinct from edgar_institutional_holdings (13F = what an investment MANAGER like Berkshire owns); this is a registered fund's own N-PORT. Covers US-registered open-end funds + ETFs; data is ~30-60 days delayed. Note: a few legacy ETFs structured as unit investment trusts (e.g. SPY, DIA) don't file N-PORT and won't resolve — use IVV or VOO for S&P 500 exposure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoTop N holdings by weight to return (1-100, default 25)
tickerYesETF or mutual-fund ticker (e.g. "ARKK", "SPY", "QQQ"). Fund tickers, not company stock tickers.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 25,
+    "ticker": "ARKK"
+  },
+  {
+    "limit": 10,
+    "ticker": "QQQ"
+  }
+]
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already indicate read-only, idempotent, non-destructive. Description adds data delay (30-60 days), coverage of US-registered funds, and notes that unit investment trusts don't file N-PORT. No contradictions with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Dense yet structured: starts with authoritative tone, then usage, output format, examples, distinction from sibling, caveats. Every sentence adds value. No fluff.

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?

Given no output schema, the description defines return contents (net assets, holdings count, top positions with name, CUSIP, value, weight). Covers exceptions (unit investment trusts) and delay. Could specify more about pagination or full output structure, but sufficient for confident use.

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%, but description adds critical nuance: 'Pass the FUND's ticker' and clarifies fund vs company tickers, preventing misuse. The description implicitly explains the limit parameter via 'top positions by weight'. Adds meaning beyond 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?

The description clearly states the tool returns portfolio holdings of US ETFs/mutual funds from SEC Form N-PORT, specifying 'what the fund actually owns'. It distinguishes from the sibling tool edgar_institutional_holdings (13F).

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?

Explicitly instructs to pass fund ticker (e.g., 'ARKK'), explains limit parameter. Provides use cases ('what does ARKK hold') and explicit 'when not to use' for legacy ETFs like SPY, suggesting alternatives (IVV/VOO). Distinguishes from edgar_institutional_holdings.

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

All Edgar toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources