Skip to main content
Glama

Edgar

by io.github.pipeworx-io
OverviewAdmin

Edgar Institutional Holdings

edgar_institutional_holdings
Read-onlyIdempotent

AUTHORITATIVE stock portfolio of a large institutional investor (SEC Form 13F-HR) — what a fund/manager owns, share counts, and position values. Pass the MANAGER's ticker or CIK (e.g. "BRK-B" or CIK "1067983" for Berkshire Hathaway; "1350694" for Bridgewater). Returns the latest quarterly 13F: top holdings aggregated by issuer with value (USD), shares, and % of portfolio, plus the report period. Use for "what does Berkshire own", "Bridgewater's biggest positions", "which funds hold $TICKER" (run per manager). Note: 13F covers US-listed long equity + options held by managers with >$100M AUM, filed ~45 days after quarter-end; it excludes shorts, cash, and non-US holdings. Values are whole USD for filings since 2023; older ones are in thousands. IMPORTANT: rows carry a put_call field and a plain-English direction. A put row is a BEARISH bet AGAINST that issuer — never report it as a holding the manager owns — and for option rows the value is the underlying's notional, not premium or capital at risk. Rank real holdings by pct_of_long_equity, and read position_summary + interpretation_note before summarising.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoTop N holdings by value to return (1-100, default 25)
ticker_or_cikYesThe institutional manager's ticker (e.g. "BRK-B") or CIK (e.g. "1067983"). NOT the held stock — the fund/manager doing the filing.

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_or_cik": "BRK-B"
+  },
+  {
+    "limit": 50,
+    "ticker_or_cik": "1067983"
+  }
+]
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and idempotentHint, but the description adds critical behavioral context: the 13F covers only US long equity + options, values differ by filing year, and put/call rows require careful interpretation (notional vs premium, bearish bets). This goes well beyond annotations.

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?

The description is front-loaded with the main purpose and includes examples and notes in a structured way. It is longer than necessary but every sentence adds value; it could be slightly more concise but remains efficient.

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?

Despite no output schema, the description thoroughly explains what is returned (holdings aggregated by issuer, value in USD, shares, % portfolio, report period, and fields like put_call, direction, etc.) and provides crucial interpretation guidance. It is complete for a complex financial data tool.

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 coverage is 100% and both parameters are described clearly in the schema. The description essentially restates the schema for 'ticker_or_cik' and 'limit' without adding new meaning. Baseline of 3 applies.

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 'stock portfolio of a large institutional investor (SEC Form 13F-HR)' with specific details like share counts and position values. It distinguishes from sibling tools by specifying the SEC form and the manager-level focus, and it provides concrete usage examples like 'what does Berkshire own'.

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?

The description gives explicit use cases ('Use for...') and mentions limitations (covers US long equity only, excludes shorts/cash, filing delay). It advises on correct interpretation of put/call rows. However, it does not explicitly contrast with the sibling 'edgar_fund_holdings' tool, which may overlap.

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