Skip to main content
Glama
edgar13f-mcp

edgar13f-mcp

by Serios16

get_holdings_as_of

Retrieve a manager's effective 13F holdings for a report period as publicly known on a given date, applying point-in-time amendment rules and citing source accessions.

Instructions

Effective 13F holdings of the manager for one report period as knowable on as_of (point-in-time and amendment rules), with the accession number(s) they come from. Large managers file tens of thousands of rows: narrow with issuer, cusip or max_positions. as_of means what was publicly filed by that date.

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": {
      "cik": "<cik>",
      "period": "<period>",
      "as_of": "<as_of>"
    },
    "name": "get_holdings_as_of"
  }
}

Input Schema

NameRequiredDescriptionDefault
cikYesSEC Central Index Key; leading zeros optional. Resolve a manager's name to its CIK with find_manager.
as_ofYesISO-8601 knowledge date: the answer uses only what was publicly filed on EDGAR by this date.
cusipNo
issuerNoKeep only rows whose name_of_issuer contains this text (case-insensitive, whitespace collapsed); combined with cusip as AND. The response lists matched_cusips.
periodYesForm 13F report period: a calendar quarter-end date.
max_positionsNoReturn only the largest positions (by value); the response adds total_positions, truncated and order.
position_typeNoForm 13F contains long positions only; any other value is declined with unsupported_request.long

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.2

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the burden and discloses important behavior: point-in-time knowledge, amendment rules, as_of defined as publicly filed by that date, large result sets, and accession number provenance. It still omits permissions, rate limits, and full response shape, so it is not fully complete.

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?

Three tight sentences with the core purpose front-loaded, followed by practical filtering guidance and a clarifying definition of as_of. There is no filler or redundant restatement.

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 retrieval tool with no output schema and no annotations, the description covers the essential point-in-time semantics, amendment behavior, row-volume caveat, filtering strategy, and accession provenance. It remains somewhat incomplete on full response structure and position_type handling, but those are partially covered in the schema.

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 description coverage is 86%, so parameter semantics are already mostly documented. The description adds practical context for narrowing results and clarifies the meaning of as_of, but does not add much beyond the schema for cik, period, position_type, or the response fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and operation: effective 13F holdings for one manager and report period as knowable on as_of, including accession number provenance. It is distinguishable from data retrieval siblings by its point-in-time holdings scope, though it does not explicitly name alternatives.

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

Usage Guidelines3/5

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

Provides useful invocation guidance by warning that large managers file tens of thousands of rows and recommending narrowing with issuer, cusip, or max_positions. It does not say when to use this tool versus diff_holdings, list_13f_filings, or find_manager.

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