secapi-mcp

Official

Overview Schema Source Related Servers Discussions Admin

institution_holdings

Retrieve an institutional investor's 13F portfolio holdings for any quarter. Includes positions, share counts, and market values using the institution's CIK.

Instructions

Get an institutional investor's 13F portfolio holdings for a given quarter. Shows positions, share counts, and market values. Requires institution CIK.

Examples:

institution_holdings({ cik: "0001067983", quarter: "2024-Q3" })
institution_holdings({ cik: "0001166559", limit: 50, sort: "weight" })

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>"
    },
    "name": "institution_holdings"
  }
}

Input Schema

Name	Required	Description	Default
`cik`	Yes	Institution CIK (10 digits, zero-padded)
`sort`	No	Sort holdings by market value, share count, or portfolio weight	value
`limit`	No
`quarter`	No	Reporting quarter e.g. "2024-Q3". Defaults to latest available.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Jul 16, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations, the description carries full burden. It explains the tool is a read operation returning positions, shares, and values, but does not disclose potential limitations like data freshness, rate limits, or error handling. Adequate but could be more exhaustive.

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?

The description is very concise: one sentence summarizing purpose, then two examples. No redundant text, and critical information is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema so description partially explains return fields (positions, shares, market values), but omits full structure, pagination, or error behavior. Acceptable for a simple list tool but not fully complete.

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 75% (all parameters described). The description adds examples and clarifies defaults (limit=25, sort='value', quarter=latest), but does not significantly extend schema meaning. Baseline of 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 clearly states it retrieves an institutional investor's 13F portfolio holdings for a given quarter, specifying the data returned (positions, share counts, market values) and the required CIK. This is specific and distinguishes it from siblings like search_institutions or analyze_filing.

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 explicitly requires institution CIK and provides examples of usage. However, it lacks explicit when-not-to-use guidance or comparisons with alternatives, though the examples and resource specificity imply its context clearly.

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

Deploy Server