Skip to main content
Glama

Valuein — SEC EDGAR Fundamentals & Smart-Money Data

Institutional Holdings (by issuer)

get_institutional_holdings
Read-onlyIdempotent

Returns top-N institutional holders of a US public company at a specific period_end (latest by default), with aggregate institutional shares, total market value, holder count, and HHI concentration (sum of squared share-of-total percentages). Sourced from Form 13F-HR via the by-issuer partition. Institutional tier only. 13F filings carry a ~45-day reporting lag — staleness_warning fires when latest data is older than 90 days.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
top_nNoMaximum holders to return, ranked by market_value_usd. Default 25, max 200.
tickerYesStock ticker symbol of the issuer — or a CIK (SEC identifier).
as_of_dateNoPoint-in-time cutoff (YYYY-MM-DD): only 13F filings ACCEPTED by SEC on or before this date are considered, applied BEFORE the latest period is resolved. A 13F/A amendment or late filing accepted after this date is excluded (zero look-ahead) — use this for survivorship-free backtests. Omit for the latest knowable book.
period_endNoQuarter-end of the 13F reporting period (YYYY-MM-DD). Omit to use the latest period available. This is a REPORTING period, NOT a point-in-time cutoff — use as_of_date for that.
lineage_detailNoPer-row provenance envelope. compact / full / off.compact

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
cikYes
rowsYes
_metaYesProvenance envelope — data lineage for every MCP response
tickerYes
aggregateYes
as_of_dateYesThe point-in-time cutoff actually applied (echo of the as_of_date input). Null when no PIT cut was requested — never confuse this with the reporting period_end.
period_endYesThe 13F REPORTING period the rows belong to — NOT a point-in-time cutoff.
company_nameYes
data_age_daysYes
holders_countYes
hhi_concentrationYes
staleness_warningYes
total_market_value_usdYes
options_positions_countYesOption positions (put_call set) excluded from totals/HHI/rows. rows[] are common-stock 13F holdings only.
total_institutional_sharesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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."
  2. Changed2 schema fields changed
    • changedInput schema / properties / ticker / description
      Previous value: -"Stock ticker symbol of the issuer."New value: +"Stock ticker symbol of the issuer — or a CIK (SEC identifier)."
    • changedInput schema / properties / ticker / pattern
      Previous value: -"^[A-Za-z.\\-]+$"New value: +"^[A-Za-z0-9.\\-]+$"
  3. 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"
      +}
  4. 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"
      +}
  5. 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"
  6. Changed7 schema fields changed
    • addedInput schema / properties / as_of_date
      Added value: +{
      +  "description": "Point-in-time cutoff (YYYY-MM-DD): only 13F filings ACCEPTED by SEC on or before this date are considered, applied BEFORE the latest period is resolved. A 13F/A amendment or late filing accepted after this date is excluded (zero look-ahead) — use this for survivorship-free backtests. Omit for the latest knowable book.",
      +  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      +  "type": "string"
      +}
    • changedInput schema / properties / period_end / description
      Previous value: -"Quarter-end of the 13F reporting period (YYYY-MM-DD). Omit to use the latest period available."New value: +"Quarter-end of the 13F reporting period (YYYY-MM-DD). Omit to use the latest period available. This is a REPORTING period, NOT a point-in-time cutoff — use as_of_date for that."
    • addedOutput schema / properties / aggregate
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "basis": {
      +      "description": "How the aggregates were scoped, e.g. 'top_25_holders'",
      +      "type": "string"
      +    },
      +    "covers_holders": {
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "has_incomplete_rows": {
      +      "description": "True when ≥1 included holder reported a null shares/market_value — the totals sum only known values and UNDERSTATE the true figure (missing ≠ zero).",
      +      "type": "boolean"
      +    },
      +    "is_partial": {
      +      "description": "True when the top-N cap was hit, so the totals understate the issuer's true book",
      +      "type": "boolean"
      +    },
      +    "note": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "basis",
      +    "is_partial",
      +    "has_incomplete_rows",
      +    "covers_holders",
      +    "note"
      +  ],
      +  "type": "object"
      +}
    • 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 confuse this with the reporting period_end.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / options_positions_count
      Added value: +{
      +  "description": "Option positions (put_call set) excluded from totals/HHI/rows. rows[] are common-stock 13F holdings only.",
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedOutput schema / properties / period_end / description
      Added value: +"The 13F REPORTING period the rows belong to — NOT a point-in-time cutoff."
    • changedOutput schema / required
      Previous value: -[
      -  "_meta",
      -  "ticker",
      -  "cik",
      -  "company_name",
      -  "period_end",
      -  "data_age_days",
      -  "staleness_warning",
      -  "total_institutional_shares",
      -  "total_market_value_usd",
      -  "hhi_concentration",
      -  "holders_count",
      -  "rows"
      -]New value: +[
      +  "_meta",
      +  "ticker",
      +  "cik",
      +  "company_name",
      +  "period_end",
      +  "as_of_date",
      +  "data_age_days",
      +  "staleness_warning",
      +  "total_institutional_shares",
      +  "total_market_value_usd",
      +  "hhi_concentration",
      +  "holders_count",
      +  "options_positions_count",
      +  "aggregate",
      +  "rows"
      +]
  7. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive traits. The description adds meaningful behavioral context: the ~45-day reporting lag and staleness_warning threshold, plus the specific partition and tier. This goes beyond the annotations and helps the agent anticipate data freshness issues.

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 two sentences that pack relevant details (what, data source, lag) without fluff. It front-loads the main return and then adds caveats. It could be slightly tighter but is well-structured and efficient.

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?

The description explains the tool's purpose, data source, lag, and staleness, which covers key behavioral aspects. An output schema exists, so return details are handled there. It does not explain error conditions or how staleness_warning should be handled, but these are minor given the schema and annotations.

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 100% with detailed parameter descriptions for top_n, ticker, as_of_date, period_end, and lineage_detail. The description does not add significant meaning beyond the schema, only restating that period_end is optional (latest by default). Since the schema carries the burden, baseline 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 the tool returns top-N institutional holders with specific aggregates (shares, market value, holder count, HHI) for a US public company, and specifies the data source (Form 13F-HR via by-issuer partition). This is a specific verb+resource and distinguishes it from siblings like get_top_holders or get_blockholders by emphasizing 'institutional tier only'.

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?

The description provides context about the data source and reporting lag, implying it is for institutional holdings, but does not explicitly mention alternatives or when not to use it. It lacks a clear 'use X instead' or exclusion condition, so usage guidance is implied rather than explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.