Skip to main content
Glama
theodor90

form4api-mcp

by theodor90
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_holdings

Read-only

Find institutional 13F-HR holdings by ticker, CUSIP, manager CIK, quarter, or minimum value to see who owns a stock or which managers hold positions in a given quarter.

Instructions

Institutional 13F-HR positions — filter by ticker (CUSIP resolved to ticker automatically), CUSIP, manager CIK, quarter, or minimum position value. Answers "who owns NVDA" or "which managers hold AAPL this quarter"; pair with get_managers to look up a manager's identity/AUM, or get_transactions to cross-reference insider activity at the same company. Requires Business plan. Paginated, max 100/page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page number. Defaults to 1.
cusipNoCUSIP identifier of the security — the standard 9-character alphanumeric security identifier (8 chars + 1 check digit), e.g. 037833100.
tickerNoStock ticker the position is in, case-insensitive (e.g. AAPL). Resolves via CUSIP → ticker mapping for issuers without direct ticker rows.
quarterNoQuarter in YYYY-Qn format, e.g. 2026-Q1. Omit for the latest available quarter.
per_pageNoResults per page. Defaults to 20, maximum 100.
min_valueNoMinimum reported position value in USD, inclusive, as of the 13F-HR filing.
manager_cikNoCIK of the institutional manager (13F-HR filer) — SEC's numeric filer identifier. Leading zeros optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedInput schema / properties / cusip / description
      Previous value: -"CUSIP identifier of the security"New value: +"CUSIP identifier of the security — the standard 9-character alphanumeric security identifier (8 chars + 1 check digit), e.g. 037833100."
    • changedInput schema / properties / manager_cik / description
      Previous value: -"CIK of the institutional manager"New value: +"CIK of the institutional manager (13F-HR filer) — SEC's numeric filer identifier. Leading zeros optional."
    • changedInput schema / properties / min_value / description
      Previous value: -"Minimum position value in USD"New value: +"Minimum reported position value in USD, inclusive, as of the 13F-HR filing."
    • changedInput schema / properties / page / description
      Previous value: -"Page number for pagination"New value: +"1-based page number. Defaults to 1."
    • changedInput schema / properties / per_page / description
      Previous value: -"Results per page (max 100)"New value: +"Results per page. Defaults to 20, maximum 100."
    • changedInput schema / properties / quarter / description
      Previous value: -"Quarter in YYYY-Qn format, e.g. 2026-Q1"New value: +"Quarter in YYYY-Qn format, e.g. 2026-Q1. Omit for the latest available quarter."
    • changedInput schema / properties / ticker / description
      Previous value: -"Stock ticker the position is in (e.g. AAPL). Resolves via CUSIP → ticker mapping for issuers without direct ticker rows."New value: +"Stock ticker the position is in, case-insensitive (e.g. AAPL). Resolves via CUSIP → ticker mapping for issuers without direct ticker rows."
  2. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare readOnly and openWorld hints. Description adds pagination limit (max 100/page) and plan requirement, which are useful behavioral details 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.

Conciseness5/5

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

Three sentences, no redundancy. Efficiently conveys resource, filters, use cases, sibling associations, and constraints (plan, pagination).

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 read-only tool with good schema and no output schema, description adequately covers functionality, filtering, pagination, and plan requirement. Missing return format details but acceptable.

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 covers all 7 parameters with descriptions (100% coverage). Description adds context like 'CUSIP resolved to ticker automatically' but mostly summarizes, not adding significant new semantics 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?

Description clearly states the tool returns institutional 13F-HR holdings with filtering options. It gives concrete use cases ('who owns NVDA') and distinguishes from siblings like get_managers and get_transactions.

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?

Provides examples of when to use and pairs with siblings for further lookups. Mentions plan requirement. Lacks explicit when-not-to-use but context is clear.

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

Deploy Server

Other Tools