FolioFact

Stock financial statements and valuation

stock_financials

Read-onlyIdempotent

Financial statements (yearly and quarterly) and the valuation summary (enterprise value, FCF/EV and OCF/EV yields). Requires FolioFact Pro.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ticker`	Yes	Stock ticker (dots allowed).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes
`series`	Yes
`ticker`	Yes
`summary`	Yes
`provenance`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 24, 2026

addedOutput schema / properties / summary / properties / valuation_basis

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "accession_number": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "calculation_version": {
+      "type": "string"
+    },
+    "cash_flow_period": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "description": {
+      "type": "string"
+    },
+    "estimated": {
+      "type": "boolean"
+    },
+    "ev_unavailable_reason": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "mapping_sources": {
+      "anyOf": [
+        {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "measurement": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "price_on": {
+      "format": "date",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "shares_on": {
+      "format": "date",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "source_url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "statement_on": {
+      "format": "date",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "unavailable_reason": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "statement_on",
+    "shares_on",
+    "price_on",
+    "measurement",
+    "estimated",
+    "description",
+    "unavailable_reason",
+    "ev_unavailable_reason",
+    "accession_number",
+    "source_url",
+    "mapping_sources",
+    "calculation_version",
+    "cash_flow_period"
+  ],
+  "type": "object"
+}

changedOutput schema / properties / summary / required

Previous value: -[
-  "market_cap",
-  "enterprise_value",
-  "fcf_ev_yield_ttm",
-  "ocf_ev_yield_ttm",
-  "fcf_ev_yield_year",
-  "ocf_ev_yield_year",
-  "price",
-  "price_reported_on",
-  "price_basis_kind",
-  "valuation_observed_at",
-  "valuation_label",
-  "revenue_growth_quarter",
-  "revenue_growth_year",
-  "revenue_growth_three_year_cagr",
-  "share_reduction_quarter",
-  "share_reduction_year",
-  "share_reduction_two_years",
-  "share_reduction_three_years"
-]New value: +[
+  "market_cap",
+  "enterprise_value",
+  "fcf_ev_yield_ttm",
+  "ocf_ev_yield_ttm",
+  "fcf_ev_yield_year",
+  "ocf_ev_yield_year",
+  "price",
+  "price_reported_on",
+  "price_basis_kind",
+  "valuation_observed_at",
+  "valuation_label",
+  "valuation_basis",
+  "revenue_growth_quarter",
+  "revenue_growth_year",
+  "revenue_growth_three_year_cagr",
+  "share_reduction_quarter",
+  "share_reduction_year",
+  "share_reduction_two_years",
+  "share_reduction_three_years"
+]

Changed5 schema fields changedAug 13, 2026

removedOutput schema / properties / summary / properties / price / anyOf

Removed value: -[
-  {
-    "pattern": "^-?[0-9]+(?:\\.[0-9]+)?$",
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / summary / properties / price / type
```
Added value: +"null"
```

changedOutput schema / properties / summary / properties / price_basis_kind / anyOf

Previous value: -[
-  {
-    "enum": [
-      "daily_close",
-      "implied_13f"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "daily_close",
+      "intraday",
+      "implied_13f"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / summary / properties / valuation_observed_at

Added value: +{
+  "format": "date-time",
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedOutput schema / properties / summary / required

Previous value: -[
-  "market_cap",
-  "enterprise_value",
-  "fcf_ev_yield_ttm",
-  "ocf_ev_yield_ttm",
-  "fcf_ev_yield_year",
-  "ocf_ev_yield_year",
-  "price",
-  "price_reported_on",
-  "price_basis_kind",
-  "valuation_label",
-  "revenue_growth_quarter",
-  "revenue_growth_year",
-  "revenue_growth_three_year_cagr",
-  "share_reduction_quarter",
-  "share_reduction_year",
-  "share_reduction_two_years",
-  "share_reduction_three_years"
-]New value: +[
+  "market_cap",
+  "enterprise_value",
+  "fcf_ev_yield_ttm",
+  "ocf_ev_yield_ttm",
+  "fcf_ev_yield_year",
+  "ocf_ev_yield_year",
+  "price",
+  "price_reported_on",
+  "price_basis_kind",
+  "valuation_observed_at",
+  "valuation_label",
+  "revenue_growth_quarter",
+  "revenue_growth_year",
+  "revenue_growth_three_year_cagr",
+  "share_reduction_quarter",
+  "share_reduction_year",
+  "share_reduction_two_years",
+  "share_reduction_three_years"
+]

AddedAug 4, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already cover readOnly, idempotent, and non-destructive behavior. The description adds the requirement for FolioFact Pro, which is a meaningful operational constraint not in the annotations. It does not disclose rate limits, pagination, or data freshness, but given the strong annotation coverage, the added Pro requirement justifies a middle score.

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 a single sentence that efficiently communicates the core content (financial statements, valuation summary) and the Pro requirement. It is front-loaded with the most important information and contains no fluff. It is concise and well-structured, though it could arguably be split into two sentences for readability.

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 the tool's moderate complexity, a single parameter, and the presence of an output schema (which covers return values), the description is largely complete. It specifies the types of data included (yearly/quarterly statements, valuation yields) and the access requirement (Pro). No major gaps are apparent for a read-only tool with a single ticker input.

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?

The schema provides 100% coverage for the single parameter 'ticker' with a clear description. The tool description does not add any parameter-specific details beyond the schema. Since coverage is complete, the baseline of 3 is appropriate, and there is no extra semantic value from the description.

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 clearly states the tool's purpose: it provides financial statements (yearly and quarterly) and a valuation summary including specific metrics like enterprise value, FCF/EV and OCF/EV yields. It uses a specific resource (financial statements and valuation) and distinguishes itself from siblings like stock_earnings and stock_options by focusing on statements and valuation, though it does not explicitly name alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description offers no guidance on when to use this tool versus alternatives like get_stock or stock_earnings. It only mentions a prerequisite ('Requires FolioFact Pro'), which is a condition for use but not a comparison to other tools. The agent must infer usage from the name and sibling context.

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

All FolioFact 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.

Resources

Need Help?