FinBridge

Get Institutional Holdings (SEC Form 13F)

get_edgar_13f

Read-only

Quarter-end institutional manager holdings reconstructed from SEC 13F-HR and 13F-HR/A (RESTATEMENT or NEW HOLDINGS), for the latest reportDate in recent submissions. Pass a manager name or CIK, not an issuer ticker. top=1–50 (default 20) limits displayed rows. response_format=markdown or json.

Returns reported security rows with separate class, PUT/CALL, SH/PRN, discretion and other-manager fields; no ticker mapping or reverse ownership lookup. Values normalize each filing to USD using the 2023-01-03 filing-date boundary. Missing numbers stay null. Duplicate/shared reporting, incomplete amendment chains and confidential omissions withhold totals/weights. sources carries accession, primary/table URLs, report/filed/acceptance/fetch times and amendment evidence.

prior_period is a distinct reportDate; no prior omits changes. Unverified corporate actions, missing rows, options/principal and incomplete reports withhold change signals with explicit comparison_exclusions. Empty changes does not establish no activity. 13F covers disclosed Section 13(f) positions, not a complete/current portfolio; 45 days is a filing deadline, not a freshness guarantee. Not investment advice.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`top`	No	Number of largest holdings by value to return (default 20)
`filer`	Yes	Institutional manager name ('Berkshire Hathaway Inc', 'Bridgewater Associates') or CIK number ('1067983')
`response_format`	No	'markdown' for tables, 'json' for compact machine-readable output	markdown

Output Schema

TableJSON Schema

Name	Required	Description	Default
`filed`	No
`filer`	Yes
`notes`	No
`period`	No
`changes`	No
`sources`	Yes
`holdings`	Yes
`value_unit`	No
`total_value`	No
`generated_at`	No
`num_holdings`	No
`prior_period`	No
`prior_sources`	No
`index_warnings`	Yes
`comparison_status`	No
`calculation_version`	No
`comparison_exclusions`	Yes
`reconstruction_status`	No
`prior_reconstruction_status`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedSep 10, 2026

addedOutput schema / properties / calculation_version

Added value: +{
+  "$ref": "#/properties/filer/properties/name"
+}

addedOutput schema / properties / comparison_exclusions

Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "properties": {},
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / comparison_status

Added value: +{
+  "$ref": "#/properties/filer/properties/name"
+}

addedOutput schema / properties / generated_at

Added value: +{
+  "$ref": "#/properties/filer/properties/name"
+}

addedOutput schema / properties / holdings / items / properties / pct_of_portfolio
```
Added value: +{
+  "$ref": "#/properties/total_value"
+}
```
addedOutput schema / properties / holdings / items / properties / put_call
```
Added value: +{
+  "$ref": "#/properties/filer/properties/name"
+}
```
addedOutput schema / properties / holdings / items / properties / quantity_type
```
Added value: +{
+  "$ref": "#/properties/filer/properties/name"
+}
```
addedOutput schema / properties / holdings / items / properties / shares
```
Added value: +{
+  "$ref": "#/properties/total_value"
+}
```
addedOutput schema / properties / holdings / items / properties / value
```
Added value: +{
+  "$ref": "#/properties/total_value"
+}
```

addedOutput schema / properties / index_warnings

Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "properties": {},
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / prior_reconstruction_status

Added value: +{
+  "$ref": "#/properties/filer/properties/name"
+}

addedOutput schema / properties / prior_sources

Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "properties": {},
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / reconstruction_status

Added value: +{
+  "$ref": "#/properties/filer/properties/name"
+}

addedOutput schema / properties / sources

Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "properties": {},
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / required

Previous value: -[
-  "filer",
-  "holdings",
-  "changes"
-]New value: +[
+  "filer",
+  "holdings",
+  "index_warnings",
+  "comparison_exclusions",
+  "sources"
+]

First observedSep 6, 2026

TDQS

A4.8/5.0

Behavior5/5

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

The description goes well beyond the readOnlyHint/openWorldHint annotations by disclosing normalization details (2023-01-03 filing-date boundary), null handling, withheld totals/weights for incomplete data, amendment evidence, and the 45-day filing deadline caveat. It also warns that empty changes does not establish no activity, which is critical behavioral context.

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 description is dense but well-organized, front-loading the core purpose and then covering caveats. It is longer than ideal, but every sentence carries meaningful behavioral or usage information. The structure is logical: purpose, parameters, return details, limitations.

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?

Given the tool's complexity (13F data, amendments, normalization, exclusions), the description is remarkably complete. It covers input requirements, output contents, edge cases, and limitations. The output schema exists, so return values don't need to be spelled out, but the description still explains the sources and changes fields.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all three parameters. The description adds value by explaining the filer parameter accepts either a name or CIK, and by clarifying the top parameter limits displayed rows. It doesn't add much beyond the schema, but the filer clarification is genuinely useful.

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 the tool reconstructs quarter-end institutional manager holdings from SEC 13F filings, and explicitly distinguishes it from issuer-ticker lookups. It names the resource (SEC 13F-HR filings) and the specific verb (get/reconstruct), making it easy to differentiate from siblings like get_edgar_filings or get_edgar_financials.

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

Usage Guidelines5/5

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

The description explicitly says to pass a manager name or CIK, not an issuer ticker, and explains the top parameter range and response_format options. It also clarifies what the tool does not do (no ticker mapping, no reverse ownership lookup), which helps an agent decide when to use it versus alternatives.

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

All FinBridge tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.