Skip to main content
Glama

Trading Signals Toolkit

SEC 13F Fund Holdings

sec_13f_holdings
Read-only

Latest SEC Form 13F-HR holdings for one fund manager, by CIK or name (e.g. berkshire, pershing square, bridgewater): top positions with ticker, CUSIP, shares, value and % of portfolio, portfolio totals, and quarter-over-quarter changes (new, added, trimmed, exited) vs the prior 13F, with period, filing date and EDGAR links. As filed, up to 45 days after quarter end; not current positions. Read-only, never places orders. Informational only, not investment advice.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sec_13f_holdings"
  }
}

Input Schema

NameRequiredDescriptionDefault
cikNoSEC CIK of the manager, e.g. 1067983 for Berkshire Hathaway
topNoNumber of top positions (default 25)
nameNoManager name if you don't know the CIK, e.g. 'pershing square'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, open-world, non-destructive and non-idempotent behavior, so the bar is lower. The description still adds real substance: the 45-day filing lag and the explicit warning that these are not current positions, plus that results are informational only. 'Read-only, never places orders' partly restates readOnlyHint but sharpens it.

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 payload sentence is front-loaded with what the tool returns, followed by two short caveat sentences that each carry a distinct warning. It is dense and long for a single sentence, but every clause conveys scope, output content, or a filing-lag caveat. Minor redundancy between 'read-only' and readOnlyHint is the only waste.

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?

There is no output schema, so the description must carry the return-value burden, and it does: field list, portfolio totals, QoQ deltas, period, filing date and EDGAR links. For a three-optional-parameter read tool, an agent has everything needed to pick it, supply args, and interpret the response.

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%, so cik, name and top are already documented in the schema, including the Berkshire CIK example and the default-25 top count. The description's name examples (berkshire, pershing square, bridgewater) add flavor but no new constraint, and it says nothing about how 'top' interacts with portfolio totals. Baseline 3 is appropriate.

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 names a specific verb and resource: 'Latest SEC Form 13F-HR holdings for one fund manager, by CIK or name.' It enumerates the returned fields (ticker, CUSIP, shares, value, % of portfolio) and the comparison set (QoQ new/added/trimmed/exited). The phrase 'for one fund manager' also makes the direction of the lookup clear against the sibling sec_13f_holders, which reads the opposite way.

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?

It gives concrete entry conditions (one manager identified by CIK or name) and supplies example name inputs so an agent knows what to pass. The 'As filed... not current positions' line tells the agent when this data is not appropriate to treat as live. It stops short of explicitly routing to sec_13f_holders or other sibling tools, so it is clear context rather than full when/when-not guidance.

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