Skip to main content
Glama

Valuein — SEC EDGAR Fundamentals & Smart-Money Data

by io.github.valuein

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
NameRequiredDescriptionDefault
top_nNoMaximum positions to return, ranked by market_value_usd. Default 25.
filer_cikNoCIK of the 13F filer (1-10 digits; will be zero-padded to 10). Preferred over filer_name when known.
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 + 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_nameNoFiler name to fuzzy-match against entity.name. Case-insensitive substring match. Multiple matches raise INVALID_ARGUMENT — use filer_cik in that case.
period_endNoQuarter-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_detailNoPer-row provenance envelope.compact

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
rowsYes
_metaYesProvenance envelope — data lineage for every MCP response
aggregateYes
filer_cikYes
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.
filer_nameYes
period_endYesThe 13F REPORTING period the positions belong to — NOT a point-in-time cutoff.
data_age_daysYes
positions_countYes
prior_period_endYes
staleness_warningYes
total_market_value_usdYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 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"
+}
  2. 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"
+}
  3. 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"
  4. Changed6 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 + 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"
+]
  5. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate readonly and idempotent. Description adds context: explains as_of_date is point-in-time cutoff with no look-ahead, period_end is reporting period, and the QoQ delta logic. No contradictions with annotations.

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 moderately concise; each sentence contributes useful information. It is front-loaded with the main purpose and then details. Could be slightly more streamlined, but no redundancy.

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 presence of a full output schema and thorough parameter descriptions, the description covers all necessary context: how to identify the filer, date options, and error handling. No missing critical details.

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

Parameters5/5

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

Schema description coverage is 100%, and the description adds extra meaning: explains the interaction between as_of_date and period_end, preferred identification method, and the effect of multiple name matches. This goes well beyond the schema definitions.

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 it returns a 13F filer's full portfolio with QoQ deltas, using specific verb 'Returns' and resource '13F filer's portfolio'. It distinguishes from siblings like get_institutional_holdings by focusing on a single filer and quarter-over-quarter changes.

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?

Provides explicit guidance on how to specify the filer (CIK preferred, name fallback), and notes that multiple name matches raise an error for disambiguation. Also mentions 'Institutional tier only', but does not explicitly contrast with sibling tools.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation5/5

Each tool has a distinct purpose with detailed descriptions that clarify differences. Overlaps like get_peer_comparables vs screen_universe are well-differentiated by scope (single company vs cross-sectional). Similarly, get_insider_sentiment vs get_smart_money_flow are clearly distinguished by data sources and methodology.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (e.g., create_report, get_financial_ratios, delete_alert). No mixing of conventions or inconsistent verbs.

Tool Count2/5

With 69 tools, the count far exceeds the 25+ threshold for 'too many'. While the domain is broad, the sheer volume likely overwhelms agents and increases selection complexity.

Completeness4/5

The tool set covers a wide range of SEC filings, ratios, smart-money data, alerts, reports, and more. Minor gaps exist (e.g., no options or detailed debt data), but most analyst workflows are supported.

Resources