Valuein — SEC EDGAR Fundamentals & Smart-Money Data

Top Holders (composite, classified)

get_top_holders

Read-onlyIdempotent

Classification-aware UNION across insider transactions (latest post_transaction_shares per insider), 13F institutional holdings, and SC 13D / 13G blockholder filings for one issuer. Each row carries holder_class ∈ {insider, institutional, blockholder_13D, blockholder_13G}. Dedupes overlapping filers by precedence (13D > 13G > institutional > insider). One call, classified cap table — Bloomberg charges separately for INSIDER, OWNER, and HDS; this consolidates them.

Input Schema

TableJSON Schema

Name	Required	Description
`top_n`	No	Maximum holders to return, ranked by shares. Default 25.
`ticker`	Yes	Issuer ticker symbol — or a CIK (SEC identifier).
`as_of_date`	No	Point-in-time cutoff (YYYY-MM-DD): only filings ACCEPTED by SEC on or before this date are considered across all three sources (institutional via accepted_at, insider via accepted_at, blockholders via accepted_at). Excludes amendments/late filings accepted after this date (zero look-ahead). Omit for the latest knowable cap table.
`period_end`	No	13F REPORTING period_end. Omit for latest. NOT a point-in-time cutoff — use as_of_date.

Output Schema

TableJSON Schema

Name	Required	Description
`cik`	Yes
`rows`	Yes
`_meta`	Yes	Provenance envelope — data lineage for every MCP response
`ticker`	Yes
`staleness`	Yes	Each source has its own as-of date and lag (13F ~45-day lag; 13D/G snapshots can be years old). Percentages from different-dated denominators are NOT directly comparable.
`as_of_date`	Yes	The point-in-time cutoff actually applied (echo of the as_of_date input). Null when no PIT cut was requested. NEVER equal to period_end unless explicitly supplied — a reporting period is not a knowable-as-of date.
`period_end`	Yes	The institutional 13F REPORTING period — NOT a point-in-time cutoff.
`company_name`	Yes
`sources_breakdown`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 18, 2026

changedOutput schema / properties / _meta / properties / fundamentals_as_of / description

Previous value: -"ISO timestamp when the FINANCIAL STATEMENTS were last rebuilt. Use THIS — not `last_updated` — when telling a user how current the fundamentals are. The snapshot is republished on every weekday price refresh while the statements are carried forward unchanged, so `last_updated` can be far more recent than the numbers it sits next to."New value: +"ISO timestamp when the FINANCIAL STATEMENTS were last rebuilt in bulk. Use THIS — not `last_updated` — when telling a user how current the cross-sectional fundamentals are. The snapshot is republished on every weekday price refresh while the statements are carried forward unchanged, so `last_updated` can be far more recent than the numbers it sits next to. It is a floor for a single filer, not a ceiling: a filer with a live partition receives its filing, facts and ratios intraday (minutes after EDGAR dissemination), so an entity-scoped read may carry a filing newer than this; cross-sectional ranks (factor scores, earnings signals) refresh with the weekly bulk export."

Changed2 schema fields changedSep 11, 2026

changedInput schema / properties / ticker / description

Previous value: -"Issuer ticker symbol."New value: +"Issuer ticker symbol — or a CIK (SEC identifier)."

changedInput schema / properties / ticker / pattern

Previous value: -"^[A-Za-z.\\-]+$"New value: +"^[A-Za-z0-9.\\-]+$"

Changed2 schema fields changedJul 25, 2026

addedOutput schema / properties / _meta / properties / fundamentals_as_of

Added value: +{
+  "description": "ISO timestamp when the FINANCIAL STATEMENTS were last rebuilt. Use THIS — not `last_updated` — when telling a user how current the fundamentals are. The snapshot is republished on every weekday price refresh while the statements are carried forward unchanged, so `last_updated` can be far more recent than the numbers it sits next to.",
+  "type": "string"
+}

addedOutput schema / properties / _meta / properties / price_as_of

Added value: +{
+  "description": "ISO timestamp when the price surfaces were last refreshed.",
+  "type": "string"
+}

Changed2 schema fields changedJul 7, 2026

addedOutput schema / properties / _meta / properties / cost_usd

Added value: +{
+  "additionalProperties": false,
+  "description": "Per-call cost transparency. Omitted for subscription-only tools that have no PAYG-equivalent price.",
+  "properties": {
+    "amount_usd": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "basis": {
+      "description": "payg_charge = real agent-pay charge. payg_rate_card = indicative price, not billed.",
+      "enum": [
+        "payg_charge",
+        "payg_rate_card"
+      ],
+      "type": "string"
+    },
+    "billed": {
+      "description": "true = this amount was actually charged via PAYG for this call. false = indicative PAYG-equivalent value; your plan already covers this call for free.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "amount_usd",
+    "billed",
+    "basis"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / _meta / properties / latency_ms

Added value: +{
+  "description": "Wall-clock milliseconds this tool call took, measured server-side around the handler.",
+  "minimum": 0,
+  "type": "integer"
+}

Changed1 schema field changedJun 18, 2026
- addedOutput schema / properties / _meta / properties / pit_safe / description
```
Added value: +"true iff a zero-look-ahead point-in-time cut was applied to every returned figure"
```

Changed13 schema fields changedJun 5, 2026

addedInput schema / properties / as_of_date

Added value: +{
+  "description": "Point-in-time cutoff (YYYY-MM-DD): only filings ACCEPTED by SEC on or before this date are considered across all three sources (institutional via accepted_at, insider via accepted_at, blockholders via accepted_at). Excludes amendments/late filings accepted after this date (zero look-ahead). Omit for the latest knowable cap table.",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}

changedInput schema / properties / period_end / description

Previous value: -"13F period_end. Omit for latest."New value: +"13F REPORTING period_end. Omit for latest. NOT a point-in-time cutoff — use as_of_date."

addedOutput schema / properties / as_of_date

Added value: +{
+  "description": "The point-in-time cutoff actually applied (echo of the as_of_date input). Null when no PIT cut was requested. NEVER equal to period_end unless explicitly supplied — a reporting period is not a knowable-as-of date.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / period_end / description

Added value: +"The institutional 13F REPORTING period — NOT a point-in-time cutoff."

removedOutput schema / properties / rows / items / properties / as_of_date
```
Removed value: -{
-  "type": "string"
-}
```

addedOutput schema / properties / rows / items / properties / co_filers

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "cik": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "name": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "cik"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Other members of the same group filing collapsed into this row (13D/G co-filers)."
+}

addedOutput schema / properties / rows / items / properties / observation_date

Added value: +{
+  "description": "Date the holding was observed (13F period_end, 13D/G as-of/filing date, or insider transaction_date). NOT a point-in-time cutoff — see the top-level as_of_date.",
+  "type": "string"
+}

addedOutput schema / properties / rows / items / properties / percent_basis

Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "of_13f_institutional_float",
+        "of_shares_outstanding"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Denominator for percent_owned. 13F = share of covered 13F float; 13D/G = percent of shares outstanding. Not comparable across bases."
+}

addedOutput schema / properties / rows / items / properties / shares / description

Added value: +"Null when the source filing did not report a share count — MISSING, not a real 0 (never emit 0 for an absent holding)."

changedOutput schema / properties / rows / items / properties / shares / type
```
Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
```

changedOutput schema / properties / rows / items / required

Previous value: -[
-  "holder_class",
-  "holder_name",
-  "holder_cik",
-  "shares",
-  "market_value_usd",
-  "percent_owned",
-  "as_of_date",
-  "source",
-  "going_active"
-]New value: +[
+  "holder_class",
+  "holder_name",
+  "holder_cik",
+  "shares",
+  "market_value_usd",
+  "percent_owned",
+  "percent_basis",
+  "observation_date",
+  "source",
+  "going_active",
+  "co_filers"
+]

addedOutput schema / properties / staleness

Added value: +{
+  "additionalProperties": false,
+  "description": "Each source has its own as-of date and lag (13F ~45-day lag; 13D/G snapshots can be years old). Percentages from different-dated denominators are NOT directly comparable.",
+  "properties": {
+    "blockholder_data_age_days": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "blockholder_staleness_warning": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "institutional_data_age_days": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "institutional_staleness_warning": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "institutional_data_age_days",
+    "institutional_staleness_warning",
+    "blockholder_data_age_days",
+    "blockholder_staleness_warning"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "_meta",
-  "ticker",
-  "cik",
-  "company_name",
-  "period_end",
-  "sources_breakdown",
-  "rows"
-]New value: +[
+  "_meta",
+  "ticker",
+  "cik",
+  "company_name",
+  "period_end",
+  "as_of_date",
+  "sources_breakdown",
+  "staleness",
+  "rows"
+]

AddedMay 10, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations declare readOnlyHint, idempotentHint, and destructiveHint false, covering the safety profile. The description adds substantial behavioral context beyond that: dedupe precedence (13D > 13G > institutional > insider), per-row holder_class classification, and the use of 'latest post_transaction_shares per insider'. This meaningfully informs the agent about aggregation and conflict-resolution behavior, which annotations do not convey.

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 dense but every sentence earns its place: scope of union, row semantics, dedupe logic, and the consolidation value proposition. No filler or repetition; the most important distinguishing trait ('Classification-aware UNION') is front-loaded.

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 composite tool with high complexity, the description covers aggregation sources, classification, dedupe precedence, and the external comparison. Combined with a 100% parameter-described schema, safety annotations, and an output schema, nothing essential is missing for correct invocation.

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 100%, with all four parameters (ticker, top_n, as_of_date, period_end) fully documented in the input schema. The description itself adds no parameter-level detail, but given the baseline rule for high coverage, a 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 names a specific verb (UNION across) and a precise resource set: insider transactions, 13F institutional holdings, and SC 13D/13G blockholder filings for one issuer. It distinguishes itself from sibling tools by adding 'classification-aware' and 'composite, classified' semantics, making its role clear relative to single-source getters like get_insider_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?

The description clearly implies when to use it: when a consolidated, classified cap table across multiple holder types is needed in one call ('One call, classified cap table'). The Bloomberg comparison (INSIDER<GO>, OWNER<GO>, HDS<GO>) frames consolidation as the value proposition, implying alternatives exist for single-source needs. However, it does not explicitly name the sibling tools (e.g., get_insider_transactions) or state exclusions, so it falls short of fully explicit guidance.

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

All Valuein — SEC EDGAR Fundamentals & Smart-Money Data 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.