Skip to main content
Glama

Valuein — SEC EDGAR Fundamentals & Smart-Money Data

by io.github.valuein
OverviewDiscussionsAdmin

Capital Allocation Profile

get_capital_allocation_profile
Read-onlyIdempotent

Get a multi-year capital allocation breakdown for a US public company. Shows how management deploys cash across all six categories — capex, R&D, M&A, dividends, buybacks, and debt — plus pre-computed deployment ratios (% of operating cash flow) and over-distribution flags. Use this tool when the user asks: how does a company allocate capital, what's the buyback-vs-dividend mix, is the company over-distributing, is growth funded by R&D or M&A, what's the cash-return-ratio trend, or any 'where does the money go' question — including owner-earnings (Buffett-style) and reinvestment-rate (Damodaran-style) analysis. Data sourced from annual 10-K filings; PIT-safe via as_of_date. R&D is included as a deployment category (the primary growth-reinvestment vehicle for knowledge-economy firms), but since it's already deducted before operating cash flow, rd_pct_ocf is INFORMATIONAL and total_deployment_pct_ocf EXCLUDES R&D to preserve the cash-flow identity (OCF = capex + M&A + dividends + buybacks + debt repayment + Δcash). The flags object carries pre-computed booleans: buybacks_exceed_fcf, total_returns_exceed_fcf (buybacks + dividends > FCF), and debt_funded_distribution (over-distribution funded by leverage vs cash). Available on all plans.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerYesStock ticker symbol, e.g. AAPL, MSFT — or a CIK (SEC identifier), e.g. '0000320193'.
as_of_dateNoPoint-in-time date (YYYY-MM-DD). Only returns facts with accepted_at on or before this date — eliminates look-ahead bias.
lookback_yearsNoNumber of fiscal years to look back from the most recent filing (1–20). Defaults to 5 years for a full capital allocation cycle.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesPer-period capital-allocation rows: capex, R&D, M&A, dividends, buybacks, debt, and deployment-mix flags
noteNo
_metaYesProvenance envelope — data lineage for every MCP response
tickerYes
as_of_dateNo
lookback_yearsYesNumber of fiscal years summarized
periods_returnedYes

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, e.g. AAPL, MSFT"New value: +"Stock ticker symbol, e.g. AAPL, MSFT — or a CIK (SEC identifier), e.g. '0000320193'."
    • 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. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "_meta": {
+      "additionalProperties": false,
+      "description": "Provenance envelope — data lineage for every MCP response",
+      "properties": {
+        "as_of_date": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "data_plan": {
+          "description": "Access plan: sample | sp500 | pro | full",
+          "type": "string"
+        },
+        "data_quality": {
+          "additionalProperties": false,
+          "description": "Server-side invariants run on this response",
+          "properties": {
+            "notes": {
+              "items": {
+                "type": "string"
+              },
+              "type": "array"
+            },
+            "validation_failed": {
+              "items": {
+                "additionalProperties": false,
+                "properties": {
+                  "detail": {
+                    "type": "string"
+                  },
+                  "rule": {
+                    "type": "string"
+                  }
+                },
+                "required": [
+                  "rule",
+                  "detail"
+                ],
+                "type": "object"
+              },
+              "type": "array"
+            },
+            "validation_passed": {
+              "items": {
+                "type": "string"
+              },
+              "type": "array"
+            }
+          },
+          "required": [
+            "validation_passed",
+            "validation_failed",
+            "notes"
+          ],
+          "type": "object"
+        },
+        "last_updated": {
+          "description": "ISO timestamp when the snapshot was exported",
+          "type": "string"
+        },
+        "limit_warnings": {
+          "description": "Soft-warning array for partial fulfillment. Each entry carries a stable subcode + remediation.options[]. AI agents pattern-match on subcode.",
+          "items": {
+            "additionalProperties": true,
+            "properties": {
+              "code": {
+                "const": "LIMIT_EXCEEDED",
+                "type": "string"
+              },
+              "current_plan": {
+                "type": "string"
+              },
+              "extensions": {
+                "additionalProperties": {},
+                "type": "object"
+              },
+              "limit_type": {
+                "type": "string"
+              },
+              "limit_value": {},
+              "remediation": {
+                "additionalProperties": true,
+                "properties": {
+                  "contact_sales": {
+                    "type": "string"
+                  },
+                  "default_action": {
+                    "type": "string"
+                  },
+                  "options": {
+                    "items": {
+                      "additionalProperties": {},
+                      "type": "object"
+                    },
+                    "type": "array"
+                  },
+                  "pricing_page": {
+                    "type": "string"
+                  }
+                },
+                "required": [
+                  "options",
+                  "default_action",
+                  "pricing_page",
+                  "contact_sales"
+                ],
+                "type": "object"
+              },
+              "requested_value": {},
+              "returned_value": {},
+              "subcode": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "code",
+              "subcode",
+              "limit_type",
+              "current_plan",
+              "remediation"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "payg_override": {
+          "additionalProperties": false,
+          "description": "Set when this single response was paid for via the agent-pay PAYG flow — the rate-limit / depth-limit checks were bypassed for this call only.",
+          "properties": {
+            "amount_cents": {
+              "type": "number"
+            },
+            "entity_scope_hash": {
+              "type": "string"
+            },
+            "meter": {
+              "type": "string"
+            },
+            "quote_id": {
+              "type": "string"
+            },
+            "retry_token_hash": {
+              "type": "string"
+            },
+            "ticker_count": {
+              "type": "number"
+            },
+            "tool": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "quote_id",
+            "tool",
+            "meter",
+            "amount_cents",
+            "ticker_count",
+            "entity_scope_hash",
+            "retry_token_hash"
+          ],
+          "type": "object"
+        },
+        "pit_safe": {
+          "type": "boolean"
+        },
+        "rate_limit": {
+          "additionalProperties": false,
+          "description": "Caller's remaining budget",
+          "properties": {
+            "limit": {
+              "type": "integer"
+            },
+            "remaining": {
+              "type": "integer"
+            },
+            "reset_at": {
+              "description": "ISO 8601 timestamp when the window resets",
+              "type": "string"
+            },
+            "window": {
+              "enum": [
+                "minute",
+                "hour"
+              ],
+              "type": "string"
+            }
+          },
+          "required": [
+            "limit",
+            "remaining",
+            "reset_at",
+            "window"
+          ],
+          "type": "object"
+        },
+        "request_id": {
+          "description": "Per-request correlation id (8-char)",
+          "type": "string"
+        },
+        "result_count": {
+          "type": "integer"
+        },
+        "schema_version": {
+          "description": "Parquet schema version from manifest.json",
+          "type": "string"
+        },
+        "snapshot": {
+          "description": "Snapshot directory name (e.g. snapshot_20260420)",
+          "type": "string"
+        },
+        "source": {
+          "const": "SEC EDGAR",
+          "type": "string"
+        },
+        "ticker": {
+          "type": "string"
+        },
+        "truncation": {
+          "additionalProperties": false,
+          "description": "Set when fewer rows were returned than requested — explains why and points to a remedy",
+          "properties": {
+            "current_plan": {
+              "type": "string"
+            },
+            "plan_limit": {
+              "minimum": 0,
+              "type": "integer"
+            },
+            "reason": {
+              "enum": [
+                "PLAN_LIMIT",
+                "DATA_NOT_AVAILABLE",
+                "FISCAL_YEAR_BOUNDARY_FILTER",
+                "OTHER"
+              ],
+              "type": "string"
+            },
+            "requested": {
+              "minimum": 0,
+              "type": "integer"
+            },
+            "returned": {
+              "minimum": 0,
+              "type": "integer"
+            },
+            "upgrade_required_for": {
+              "type": "string"
+            },
+            "upgrade_url": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "requested",
+            "returned",
+            "reason"
+          ],
+          "type": "object"
+        }
+      },
+      "required": [
+        "data_plan",
+        "schema_version",
+        "snapshot",
+        "last_updated",
+        "source",
+        "pit_safe"
+      ],
+      "type": "object"
+    },
+    "as_of_date": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "data": {
+      "description": "Per-period capital-allocation rows: capex, R&D, M&A, dividends, buybacks, debt, and deployment-mix flags",
+      "items": {
+        "additionalProperties": true,
+        "properties": {},
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "lookback_years": {
+      "description": "Number of fiscal years summarized",
+      "type": "integer"
+    },
+    "note": {
+      "type": "string"
+    },
+    "periods_returned": {
+      "type": "integer"
+    },
+    "ticker": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "_meta",
+    "ticker",
+    "lookback_years",
+    "periods_returned",
+    "data"
+  ],
+  "type": "object"
+}
  7. Changed1 schema field changed
    • changedInput schema / properties / as_of_date / description
      Previous value: -"Point-in-time date (YYYY-MM-DD). Only returns facts with knowledge_at on or before this date — eliminates look-ahead bias."New value: +"Point-in-time date (YYYY-MM-DD). Only returns facts with accepted_at on or before this date — eliminates look-ahead bias."
  8. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnly/idempotent, so the description carries the full behavioral burden and exceeds it: it discloses the 10-K source, PIT-safe semantics via as_of_date, the R&D exclusion from total_deployment_pct_ocf to preserve the cash-flow identity, and the exact meaning of each flag. No contradiction 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 long but information-dense and front-loads the core output before use cases and caveats. Some non-essential framing (Buffett/Damodaran labels, 'Available on all plans') could be trimmed, but the structure is otherwise efficient for a tool with this much nuance.

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?

With an output schema handling the return structure, the description covers everything else needed for correct invocation: what the tool returns, what question types it serves, data provenance, PIT behavior, the R&D accounting caveat, and the flag semantics. No material gap remains.

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%, so the schema already documents all three parameters; the baseline is therefore 3. The description reinforces as_of_date's point-in-time role and implies lookback_years via 'multi-year', but it doesn't add meaningful semantics beyond what the schema provides.

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?

Description opens with a specific verb and resource: 'Get a multi-year capital allocation breakdown for a US public company.' It enumerates the six deployment categories, the pre-computed ratios, and the flags, making the tool's scope unmistakable and distinguishing it from financial-data siblings like get_financial_ratios or get_valuation_metrics.

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 explicitly lists trigger questions ('how does a company allocate capital', 'buyback-vs-dividend mix', 'where does the money go') and the analytical styles it supports. It does not, however, name sibling alternatives or state when not to use this tool, so it stops just short of perfect 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 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