FiledProof

Reconcile one SEC financial fact

filedproof.reconcile_financial_fact

Read-onlyIdempotent

$1.00 USD specialist operation when commerce is active. Use this for one supported quarterly or fiscal-year revenue, net income, or operating cash flow fact. Optionally provide comparison_accession plus comparison_value to verify that number against an SEC-filed 8-K earnings-release exhibit and assess GAAP/non-GAAP, period, currency, and scope comparability. Arithmetic bridges are returned only when visible source rows reproduce exactly; otherwise the reason remains unresolved. Use filedproof.preflight_financial_fact first when eligibility is uncertain, filedproof.verify_claim for a narrative factual proposition, or filedproof.search_evidence for general filing research. Unsupported or ambiguous requests abstain before payment.

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
`asOf`	Yes
`scale`	No
`scope`	Yes
`units`	No
`value`	Yes
`issuer`	Yes
`period`	Yes
`source`	Yes
`status`	Yes
`currency`	Yes
`evidence`	Yes
`resultId`	Yes
`operation`	Yes
`derivation`	Yes
`validation`	Yes
`limitations`	Yes
`resultBasis`	Yes
`anchorFiling`	Yes
`schemaVersion`	Yes
`resolvedMetric`	Yes
`canonicalRequest`	Yes
`originalReported`	Yes
`revisionAssessment`	Yes
`unresolvedQuestions`	Yes
`numberReconciliation`	No
`subsequentReportedValues`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 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 / numberReconciliation

Added value: +{
+  "type": [
+    "object",
+    "null"
+  ]
+}

Changed19 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"
+]

addedOutput schema / properties / asOf
```
Added value: +{
+  "type": "object"
+}
```
addedOutput schema / properties / issuer
```
Added value: +{
+  "type": "object"
+}
```

addedOutput schema / properties / originalReported

Added value: +{
+  "type": [
+    "object",
+    "null"
+  ]
+}

addedOutput schema / properties / revisionAssessment
```
Added value: +{
+  "type": "object"
+}
```

addedOutput schema / properties / scale

Added value: +{
+  "type": [
+    "integer",
+    "null"
+  ]
+}

addedOutput schema / properties / subsequentReportedValues
```
Added value: +{
+  "type": "array"
+}
```

addedOutput schema / properties / units

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / unresolvedQuestions

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedOutput schema / required

Previous value: -[
-  "schemaVersion",
-  "operation",
-  "resultId",
-  "status",
-  "canonicalRequest",
-  "resolvedMetric",
-  "period",
-  "scope",
-  "source",
-  "anchorFiling",
-  "value",
-  "currency",
-  "resultBasis",
-  "derivation",
-  "evidence",
-  "validation",
-  "limitations"
-]New value: +[
+  "schemaVersion",
+  "operation",
+  "resultId",
+  "status",
+  "canonicalRequest",
+  "issuer",
+  "resolvedMetric",
+  "period",
+  "asOf",
+  "scope",
+  "source",
+  "anchorFiling",
+  "value",
+  "currency",
+  "resultBasis",
+  "derivation",
+  "evidence",
+  "originalReported",
+  "subsequentReportedValues",
+  "revisionAssessment",
+  "validation",
+  "limitations",
+  "unresolvedQuestions"
+]

Changed1 schema field changedSep 13, 2026

addedInput schema / properties / metric / description

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

AddedSep 13, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond annotations (readOnly, openWorld, idempotent), the description discloses the $1.00 USD cost when commerce is active, the condition that arithmetic bridges appear only when visible source rows reproduce exactly, and that unsupported requests abstain before payment. These are meaningful behavioral details not present in 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?

Five sentences, front-loaded with purpose and cost, then usage, limitation, and alternatives. Every sentence carries essential information with no filler or redundant restatement.

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 tool's complexity (12 params, output schema), the description covers purpose, usage, limitations, cost, and alternatives. An output schema exists, so return values need not be described. Nothing essential for correct selection or invocation is missing.

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 baseline is 3. The description adds context for comparison_accession and comparison_value and mentions anchor filing selection, but it does not materially change parameter understanding beyond the schema's own descriptions.

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 the specific verb 'Reconcile' with resource 'one SEC financial fact' and defines supported metrics (revenue, net income, operating cash flow) and period types. Explicitly distinguishes from siblings by naming preflight, verify_claim, and search_evidence as alternatives.

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?

Provides explicit when-to-use guidance ('Use this for one supported...'), when-to-use alternatives ('Use filedproof.preflight_financial_fact first when eligibility is uncertain...'), and describes the optional comparison flow. Also states the abstention rule for unsupported or ambiguous requests.

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?