Valuein — SEC EDGAR Fundamentals & Smart-Money Data

Manager Portfolio (13F by filer)

get_manager_portfolio

Read-onlyIdempotent

Returns a 13F filer's full portfolio at a specific period_end (latest by default), with QoQ deltas vs the prior quarter (new / increased / decreased / exited / unchanged). Specify the filer either by filer_cik (preferred) or filer_name (fuzzy match against entity.name; multiple matches raise an ambiguity error so you can disambiguate by CIK). Institutional tier only.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`top_n`	No	Maximum positions to return, ranked by market_value_usd. Default 25.
`filer_cik`	No	CIK of the 13F filer (1-10 digits; will be zero-padded to 10). Preferred over filer_name when known.
`as_of_date`	No	Point-in-time cutoff (YYYY-MM-DD): only 13F filings ACCEPTED by SEC on or before this date are considered, applied BEFORE the latest + prior periods (and the QoQ basis) are resolved. A 13F/A amendment or late filing accepted after this date is excluded (zero look-ahead). Omit for the latest knowable portfolio.
`filer_name`	No	Filer name to fuzzy-match against entity.name. Case-insensitive substring match. Multiple matches raise INVALID_ARGUMENT — use filer_cik in that case.
`period_end`	No	Quarter-end (YYYY-MM-DD). Omit to use latest available. This is a REPORTING period, NOT a point-in-time cutoff — use as_of_date for that.
`lineage_detail`	No	Per-row provenance envelope.	compact

Output Schema

TableJSON Schema

Name	Required	Description
`rows`	Yes
`_meta`	Yes	Provenance envelope — data lineage for every MCP response
`aggregate`	Yes
`filer_cik`	Yes
`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 confuse this with the reporting period_end.
`filer_name`	Yes
`period_end`	Yes	The 13F REPORTING period the positions belong to — NOT a point-in-time cutoff.
`data_age_days`	Yes
`positions_count`	Yes
`prior_period_end`	Yes
`staleness_warning`	Yes
`total_market_value_usd`	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 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"
```

Changed6 schema fields changedJun 5, 2026

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 + prior periods (and the QoQ basis) are resolved. A 13F/A amendment or late filing accepted after this date is excluded (zero look-ahead). Omit for the latest knowable portfolio.",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}

changedInput schema / properties / period_end / description

Previous value: -"Quarter-end (YYYY-MM-DD).  Omit to use latest available."New value: +"Quarter-end (YYYY-MM-DD).  Omit to use latest 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": {
+      "type": "string"
+    },
+    "covers_positions": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "has_incomplete_rows": {
+      "description": "True when ≥1 included position reported a null shares/market_value — the total sums only known values and UNDERSTATES the true book (missing ≠ zero).",
+      "type": "boolean"
+    },
+    "is_partial": {
+      "type": "boolean"
+    },
+    "note": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "basis",
+    "is_partial",
+    "has_incomplete_rows",
+    "covers_positions",
+    "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 / period_end / description

Added value: +"The 13F REPORTING period the positions belong to — NOT a point-in-time cutoff."

changedOutput schema / required

Previous value: -[
-  "_meta",
-  "filer_cik",
-  "filer_name",
-  "period_end",
-  "prior_period_end",
-  "data_age_days",
-  "staleness_warning",
-  "total_market_value_usd",
-  "positions_count",
-  "rows"
-]New value: +[
+  "_meta",
+  "filer_cik",
+  "filer_name",
+  "period_end",
+  "prior_period_end",
+  "as_of_date",
+  "data_age_days",
+  "staleness_warning",
+  "total_market_value_usd",
+  "positions_count",
+  "aggregate",
+  "rows"
+]

AddedMay 10, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, lowering the bar. The description adds valuable behavior beyond those flags: fuzzy-match behavior against entity.name, an explicit ambiguity-error condition, 'latest by default', QoQ delta classification, and an 'Institutional tier only' constraint. This is solid supplemental context.

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?

Three sentences with no filler. The primary behavior and default behavior are front-loaded, followed by the disambiguation guidance. Every sentence contributes actionable information for tool selection and invocation.

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 rich annotations, 100% schema parameter coverage, and presence of an output schema, the description is complete enough for an agent to invoke the tool correctly. It covers scope, defaults, delta behavior, disambiguation, and tier restriction; nothing essential for selecting and calling is missing.

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 description coverage is 100%, so the baseline is 3. The description adds meaningful parameter semantics beyond the schema by marking filer_cik as preferred, explaining filer_name as a fuzzy match against entity.name, and instructing the agent to disambiguate via CIK on multiple matches. This improves correct parameter selection.

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 states a specific verb and resource: 'Returns a 13F filer's full portfolio at a specific period_end', and uniquely distinguishes the tool by mentioning QoQ deltas and the CIK/name selection. This is enough for an agent to separate it from sibling tools like get_institutional_holdings or compare_periods without opening schemas.

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 gives clear selection guidance between filer_cik and filer_name, and notes the ambiguity error when multiple names match. However, it does not explicitly state when to prefer this tool over alternatives such as get_institutional_holdings or compare_periods, nor does it give exclusions; usage context is implied but not framed as alternative 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 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.