FiledProof

Check financial fact applicability

filedproof.preflight_financial_fact

Read-onlyIdempotent

Free eligibility check for filedproof.reconcile_financial_fact. Use this before the $1 specialist operation when issuer identity, filing selection, supported metric, fiscal-period dates, annual-versus-quarter context, required SEC Company Facts contexts, or an optional SEC-filed 8-K earnings-release number comparison may be uncertain. It validates applicability without revealing the filing value, comparison source value, later revision values, evidence, or arithmetic. For general filing lookup or narrative research, use filedproof.resolve_issuer, filedproof.list_filings, or filedproof.search_evidence instead.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`cik`	No	Legacy/direct SEC CIK input. Prefer identifier when starting from a ticker or company name.
`metric`	Yes	Financial metric to reconcile: revenue, net income, or operating cash flow.
`as_of_date`	No	Optional historical cutoff. The selected anchor filing must have been filed on or before this date; later values never replace the primary answer.
`identifier`	No	Issuer ticker, exact company name, CIK, or CIK-prefixed identifier. FiledProof resolves this to the durable SEC CIK before research and payment.
`period_end`	Yes	Requested fiscal-period end date.
`period_type`	No	Whether the requested value is one standalone fiscal quarter or the full fiscal year.	standalone_fiscal_quarter
`period_start`	Yes	Requested fiscal-period start date.
`anchor_accession`	No	Optional 10-Q/10-K accession, including amendments. If omitted, FiledProof selects the earliest compatible filing for the requested period.
`comparison_value`	No	Actual-unit integer value claimed from the SEC-filed earnings-release exhibit. FiledProof must find this value in metric context before the comparison is eligible.
`comparison_exhibit`	No	Optional exact EX-99 exhibit filename or safe relative path when an 8-K contains multiple candidate earnings-release exhibits.
`comparison_accession`	No	Optional SEC 8-K/8-K/A accession containing an earnings-release exhibit to compare with the filing-anchored GAAP fact. Provide comparison_value with it.
`include_subsequent_revisions`	No	When true, report later different values for the same SEC concept, unit, and period separately from the primary anchored value.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`price`	Yes
`checks`	Yes
`reason`	No
`status`	Yes
`eligible`	Yes
`operation`	Yes
`schemaVersion`	Yes
`paymentMethods`	Yes
`canonicalRequest`	Yes
`disclosureBoundary`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedSep 24, 2026

addedInput schema / properties / comparison_accession

Added value: +{
+  "description": "Optional SEC 8-K/8-K/A accession containing an earnings-release exhibit to compare with the filing-anchored GAAP fact. Provide comparison_value with it.",
+  "pattern": "^\\d{10}-\\d{2}-\\d{6}$",
+  "type": "string"
+}

addedInput schema / properties / comparison_exhibit

Added value: +{
+  "description": "Optional exact EX-99 exhibit filename or safe relative path when an 8-K contains multiple candidate earnings-release exhibits.",
+  "maxLength": 240,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / comparison_value

Added value: +{
+  "description": "Actual-unit integer value claimed from the SEC-filed earnings-release exhibit. FiledProof must find this value in metric context before the comparison is eligible.",
+  "pattern": "^-?\\d+$",
+  "type": "string"
+}

addedOutput schema / properties / checks / properties / comparisonRequested
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / checks / properties / comparisonSourceAvailable
```
Added value: +{
+  "type": "boolean"
+}
```

changedOutput schema / properties / checks / required

Previous value: -[
-  "issuerValid",
-  "anchorFilingValid",
-  "metricSupported",
-  "requestedPeriodPlausible",
-  "requiredContextDataAvailable"
-]New value: +[
+  "issuerValid",
+  "anchorFilingValid",
+  "metricSupported",
+  "requestedPeriodPlausible",
+  "comparisonRequested",
+  "comparisonSourceAvailable",
+  "requiredContextDataAvailable"
+]

Changed10 schema fields changedSep 24, 2026

addedInput schema / anyOf

Added value: +[
+  {
+    "required": [
+      "identifier"
+    ]
+  },
+  {
+    "required": [
+      "cik"
+    ]
+  }
+]

changedInput schema / properties / anchor_accession / description

Previous value: -"One non-amended 10-Q or 10-K accession that anchors the requested fiscal quarter."New value: +"Optional 10-Q/10-K accession, including amendments. If omitted, FiledProof selects the earliest compatible filing for the requested period."

addedInput schema / properties / as_of_date

Added value: +{
+  "description": "Optional historical cutoff. The selected anchor filing must have been filed on or before this date; later values never replace the primary answer.",
+  "format": "date",
+  "type": "string"
+}

changedInput schema / properties / cik / description

Previous value: -"SEC Central Index Key for one issuer."New value: +"Legacy/direct SEC CIK input. Prefer identifier when starting from a ticker or company name."

addedInput schema / properties / identifier

Added value: +{
+  "description": "Issuer ticker, exact company name, CIK, or CIK-prefixed identifier. FiledProof resolves this to the durable SEC CIK before research and payment.",
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / include_subsequent_revisions

Added value: +{
+  "default": true,
+  "description": "When true, report later different values for the same SEC concept, unit, and period separately from the primary anchored value.",
+  "type": "boolean"
+}

changedInput schema / properties / period_end / description

Previous value: -"Standalone fiscal-quarter end date."New value: +"Requested fiscal-period end date."

changedInput schema / properties / period_start / description

Previous value: -"Standalone fiscal-quarter start date."New value: +"Requested fiscal-period start date."

addedInput schema / properties / period_type

Added value: +{
+  "default": "standalone_fiscal_quarter",
+  "description": "Whether the requested value is one standalone fiscal quarter or the full fiscal year.",
+  "enum": [
+    "standalone_fiscal_quarter",
+    "fiscal_year"
+  ],
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "cik",
-  "anchor_accession",
-  "metric",
-  "period_start",
-  "period_end"
-]New value: +[
+  "metric",
+  "period_start",
+  "period_end"
+]

Changed2 schema fields changedSep 13, 2026

addedInput schema / properties / metric / description

Added value: +"Financial metric to reconcile: revenue, net income, or operating cash flow."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "canonicalRequest": {
+      "type": "object"
+    },
+    "checks": {
+      "additionalProperties": false,
+      "properties": {
+        "anchorFilingValid": {
+          "type": "boolean"
+        },
+        "issuerValid": {
+          "type": "boolean"
+        },
+        "metricSupported": {
+          "type": "boolean"
+        },
+        "requestedPeriodPlausible": {
+          "type": "boolean"
+        },
+        "requiredContextDataAvailable": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "issuerValid",
+        "anchorFilingValid",
+        "metricSupported",
+        "requestedPeriodPlausible",
+        "requiredContextDataAvailable"
+      ],
+      "type": "object"
+    },
+    "disclosureBoundary": {
+      "type": "string"
+    },
+    "eligible": {
+      "type": "boolean"
+    },
+    "operation": {
+      "const": "filedproof.reconcile_financial_fact"
+    },
+    "paymentMethods": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "price": {
+      "additionalProperties": false,
+      "properties": {
+        "cents": {
+          "minimum": 0,
+          "type": "integer"
+        },
+        "currency": {
+          "maxLength": 3,
+          "minLength": 3,
+          "type": "string"
+        }
+      },
+      "required": [
+        "cents",
+        "currency"
+      ],
+      "type": "object"
+    },
+    "reason": {
+      "type": "string"
+    },
+    "schemaVersion": {
+      "const": "financial-fact-preflight.v1"
+    },
+    "status": {
+      "enum": [
+        "eligible",
+        "ineligible"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "schemaVersion",
+    "operation",
+    "canonicalRequest",
+    "status",
+    "eligible",
+    "checks",
+    "price",
+    "paymentMethods",
+    "disclosureBoundary"
+  ],
+  "type": "object"
+}

AddedSep 13, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, but the description adds meaningful behavior beyond those: it 'validates applicability without revealing the filing value, comparison source value, later revision values, evidence, or arithmetic.' This tells the agent the tool intentionally withholds sensitive outputs, which is critical for setting expectations. It also states the operation is free, a useful cost signal. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, each earning its place: the first defines the tool, the second details when to use it and what it withholds, the third routes to alternatives. It is front-loaded with the core purpose and uses a compact list to avoid vague prose. No filler or repetition.

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?

For a tool with 12 parameters and an output schema, the description covers the essential operational context: relationship to the paid reconcile operation, the uncertainty triggers, the privacy behavior, and sibling routing. It doesn't explicitly state what the eligibility result looks like, but the output schema already covers return values. A slight gap is not defining 'eligibility' precisely (e.g., what a true/false result means for downstream calls), which would push it to a 5.

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 baseline is 3 per the rubric. The description indirectly references the parameter categories ('issuer identity, filing selection, supported metric, fiscal-period dates, annual-versus-quarter context, required SEC Company Facts contexts, or an optional SEC-filed 8-K earnings-release number comparison') which map to identifier/cik, anchor_accession, metric, period_start/end, period_type, and comparison_* fields. However, it adds no concrete semantics beyond what the schema already documents for individual parameters.

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?

States a specific verb and resource: it is a 'Free eligibility check for filedproof.reconcile_financial_fact', which clearly identifies it as a prerequisite validation step for a named specialist operation. It also distinguishes itself from siblings by naming alternative tools (resolve_issuer, list_filings, search_evidence) for different use cases. An agent can tell exactly what this tool is for without needing to open other schemas.

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

Usage Guidelines5/5

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

Explicitly tells the agent when to invoke it: 'Use this before the $1 specialist operation when ... may be uncertain', and enumerates the specific uncertainty dimensions (issuer identity, filing selection, metric, dates, period type, SEC contexts, 8-K comparison). It also gives clear exclusions: 'For general filing lookup or narrative research, use ... instead.' This is model guidance for tool selection.

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

All FiledProof 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?