Skip to main content
Glama
Sign In

Valuein — SEC EDGAR Fundamentals & Smart-Money Data

by io.github.valuein
OverviewDiscussionsAdmin

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

NameRequiredDescriptionDefault
top_nNoMaximum holders to return, ranked by shares. Default 25.
tickerYesIssuer ticker symbol — or a CIK (SEC identifier).
as_of_dateNoPoint-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_endNo13F REPORTING period_end. Omit for latest. NOT a point-in-time cutoff — use as_of_date.
include_supersededNoDefault false: 13F-HR rows replaced by a later 13F-HR/A are hidden once the amendment is knowable (as of as_of_date when given), so an original and its amendment are never both counted. Set true to include the superseded originals.

Output Schema

NameRequiredDescriptionDefault
cikYes
rowsYes
_metaYesProvenance envelope — data lineage for every MCP response
tickerYes
stalenessYesEach 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_dateYesThe 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_endYesThe institutional 13F REPORTING period — NOT a point-in-time cutoff.
company_nameYes
sources_breakdownYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / rows / items / properties / metrics_display
      Added value: +{
+  "additionalProperties": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "description": "This holder's shares, market value and percent_owned rendered for prose ('1.28B shares', '$347.72B', '8.45%'). QUOTE THESE VERBATIM.",
+  "type": "object"
+}
  2. Changed1 schema field changed
    • changedOutput schema / properties / _meta / properties / cost_usd / properties / basis / description
      Previous value: -"payg_charge = real charge (agent-pay or your balance). payg_rate_card = indicative price, not billed."New value: +"payg_charge = real pay-per-call charge (a card or MPP payment through agent-pay). payg_rate_card = indicative price, not billed."
  3. Changed2 schema fields changed
    • changedOutput schema / properties / _meta / properties / cost_usd / properties / basis / description
      Previous value: -"payg_charge = real agent-pay charge. payg_rate_card = indicative price, not billed."New value: +"payg_charge = real charge (agent-pay or your balance). payg_rate_card = indicative price, not billed."
    • changedOutput schema / properties / _meta / properties / cost_usd / properties / billed / description
      Previous value: -"true = this amount was actually charged via PAYG for this call. false = indicative PAYG-equivalent value; your plan already covers this call for free."New value: +"true = this amount was actually charged via PAYG for this call. false = indicative PAYG-equivalent value only: no charge was made for this call (it was within your plan)."
  4. Changed1 schema field changed
    • addedInput schema / properties / include_superseded
      Added value: +{
+  "default": false,
+  "description": "Default false: 13F-HR rows replaced by a later 13F-HR/A are hidden once the amendment is knowable (as of as_of_date when given), so an original and its amendment are never both counted. Set true to include the superseded originals.",
+  "type": "boolean"
+}
  5. Added
  6. Removed
  7. Changed1 schema field changed
    • 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."
  8. Changed2 schema fields changed
    • 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.\\-]+$"
  9. Changed2 schema fields changed
    • 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"
+}
  10. Changed2 schema fields changed
    • 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"
+}
  11. Changed1 schema field changed
    • 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"
  12. Changed13 schema fields changed
    • 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"
+]
  13. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-obvious behavior beyond that: per-insider latest post_transaction_shares, cross-source dedupe by precedence (13D > 13G > institutional > insider), and amendment/superseded handling. It does not discuss cost, rate limits, or output shape, which the output schema covers anyway.

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?

Four sentences, front-loaded with the core scope and row-classification contract, then dedupe rules, then the value proposition. Dense with useful detail and little waste; the Bloomberg terminal analogy is the only sentence that is closer to marketing than specification, though it does convey consolidation.

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?

Given rich annotations, a fully documented 5-parameter schema, and an existing output schema, the description covers what remains: the union logic, the holder_class taxonomy, dedupe precedence, and amendment suppression. The main residual gap is that it never routes the agent to or away from the single-source sibling tools.

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% and each parameter (ticker/CIK, top_n, as_of_date vs period_end, include_superseded) is already documented in detail in the schema, including the point-in-time semantics and the explicit warning that period_end is not a cutoff. The description adds no parameter-level meaning of its own, so the baseline 3 applies.

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?

The description states a specific operation (a UNION across insider transactions, 13F holdings, and SC 13D/13G filings for one issuer) and names the output shape (holder_class enum), so the resource and scope are unambiguous. It implicitly differentiates itself from single-source siblings like get_institutional_holdings or get_blockholders by framing itself as a composite, but never names those siblings explicitly.

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?

Usage is implied: 'One call, classified cap table' suggests this replaces three separate pulls, and the Bloomberg INSIDER<GO>/OWNER<GO>/HDS<GO> analogy reinforces the consolidation value. However, there is no explicit when-to-use/when-not statement and no named alternative tool (e.g., use get_insider_transactions when you only need insider rows), so the agent must infer the routing.

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 toolsInspect
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.

Resources