Skip to main content
Glama

Trading Signals Toolkit

SEC 13F Notable Holders of a Stock

sec_13f_holders
Read-only

Which notable fund managers (Berkshire Hathaway, Pershing Square, Bridgewater, Baupost, Duquesne, Appaloosa, Soros, Tiger Global, Coatue, ARK and ~17 more) hold a stock in their latest SEC 13F-HR: shares, value, % of each portfolio and quarter-over-quarter change (new, added, trimmed, exited). As filed, up to 45 days after quarter end. Read-only, never places orders. Informational only, not investment advice.

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": {
      "ticker": "<ticker>"
    },
    "name": "sec_13f_holders"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYesUS stock ticker, e.g. AAPL

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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, destructiveHint=false and openWorldHint, but the description adds material context beyond them: the 45-day post-quarter filing lag (data staleness), 'never places orders', and 'Informational only, not investment advice'. Those are exactly the traits an agent needs to avoid over-trusting the output, and nothing contradicts the 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?

It is one dense, front-loaded paragraph that leads with the payoff and then the return fields. The long list of ~26 example fund names is useful social proof but consumes a lot of the sentence; trimming would have lost some of the 'notable' definition, so the cost is largely justified.

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?

For a one-parameter lookup tool with no output schema, the description fully carries the load: it names the returned fields (shares, value, % of portfolio, quarter-over-quarter change), the change categories, and the filing-lag constraint. An agent could invoke and interpret this tool without further context.

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?

There is a single parameter, and the input schema fully covers it (ticker with a regex pattern and an 'AAPL' example, 100% coverage). The description adds no ticker syntax, exchange, or format guidance beyond the schema, so the 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 states a specific verb and resource: it returns 'which notable fund managers ... hold a stock in their latest SEC 13F-HR'. The direction is unambiguous (stock → holders), which implicitly distinguishes it from the inverse-style sibling 'sec_13f_holdings', and the enumerated fund names remove any doubt about what counts as 'notable'.

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 makes clear the use case: find institutional holders of a given ticker from the latest filed 13F-HR. It also adds a critical recency caveat ('As filed, up to 45 days after quarter end') that tells the agent when the data is not current. It stops short of naming an alternative sibling or an explicit 'do not use' condition, keeping it from a 5.

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