Valuein — SEC EDGAR Fundamentals & Smart-Money Data

Score Claim

score_claim

Idempotent

Resolve a claim's outcome. By default auto-grades an auto claim by evaluating its verifiable_condition against SEC fundamentals (confirmed/refuted), or marks it needs_review when it can't be resolved deterministically (judgment, antecedent, or missing data). To record a human/agent judgment instead, pass manual_status (+ optional score/reason). Idempotent — re-scoring the same resolution is a no-op.

Tier: sp500+ (sample rejected).

Input Schema

TableJSON Schema

Name	Required	Description
`as_of`	No	Snapshot date for the fundamentals window (auto mode). Defaults to today UTC.
`claim_id`	Yes	Id of the claim to resolve.
`manual_score`	No	Outcome score in [-1,1] for a manual resolution. Null for non-scored statuses.
`manual_reason`	No	Explanation for a manual resolution.
`manual_status`	No	Provide to record a human/agent outcome instead of auto-grading.

Output Schema

TableJSON Schema

Name	Required	Description
`mode`	Yes
`_meta`	Yes	Provenance envelope — data lineage for every MCP response
`basis`	Yes
`claim`	Yes
`score`	Yes
`reason`	Yes
`deduplicated`	Yes
`resolved_status`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 18, 2026

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."

Changed2 schema fields changedJul 25, 2026

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"
+}

Changed2 schema fields changedJul 7, 2026

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"
+}

Changed1 schema field changedJul 3, 2026

addedOutput schema / properties / claim / properties / outcome_components

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": {},
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Phase C resolved-metric breakdown ({evaluated, basis} from gradeClaim). Null when not yet resolved or resolved without a breakdown (manual); absent entirely on claims resolved before Phase C shipped — both mean 'no components recorded'."
+}

Changed1 schema field changedJun 23, 2026

addedOutput schema / properties / claim / properties / evidence / properties / source_links

Added value: +{
+  "description": "On-read enrichment of source_urls with interactive SEC viewer links.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "document_url": {
+        "description": "Direct link to the rendered primary document, or null.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "inline_viewer_url": {
+        "description": "SEC Inline-XBRL viewer on the rendered filing, or null when not iXBRL.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "sec_url": {
+        "description": "EDGAR filing-index page — always resolves.",
+        "type": "string"
+      },
+      "url": {
+        "description": "The original stored source_url (verbatim).",
+        "type": "string"
+      }
+    },
+    "required": [
+      "url",
+      "sec_url",
+      "document_url",
+      "inline_viewer_url"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

Changed1 schema field changedJun 18, 2026
- 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"
```

Changed1 schema field changedJun 5, 2026

changedOutput schema / properties / claim / properties / evidence / properties / fact_ids / description

Previous value: -"fact_ids backing the claim. Cross-checked against lineage at grade time."New value: +"fact_ids backing the claim. Verified against live SEC data at save time (rejected if unresolvable)."

AddedMay 28, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already provide idempotentHint=true and readOnlyHint=false. The description adds meaningful behavioral detail: the auto-grading logic, conditions for needs_review, the idempotency guarantee, and the tier restriction. This goes beyond the structured annotations but does not cover all side effects (e.g., explicit state mutation wording), so a 4 is appropriate.

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 reasonably concise, with the main purpose front-loaded and tier info placed at the end. It uses two paragraphs and about five sentences; each sentence carries useful information, though it is slightly less tight than the two-sentence ideal.

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 presence of an output schema (not shown) and strong annotations, the description covers the central behavior, modes, idempotency, and eligibility. It omits edge-case behaviors such as error handling for nonexistent claim_id, but for a tool with this complexity and annotation coverage, the description is sufficient for correct invocation.

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

Parameters4/5

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

Schema coverage is 100%, giving a baseline of 3. The description adds semantic value by explaining the relationship between manual_status and manual_score/manual_reason, and by clarifying that as_of applies only in auto mode. This contextualizes the parameters beyond their individual schema descriptions.

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 resolves a claim's outcome, with a specific verb ('resolve') and resource ('claim's outcome'), and describes the auto-grading and manual-status modes. It does not explicitly name sibling tools like score_due_claims, so the differentiation is implicit rather than explicit, preventing a 5.

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

Usage Guidelines3/5

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

The description gives clear guidance on when to use auto-grading versus manual_status, and includes the eligibility constraint 'Tier: sp500+ (sample rejected).' However, it does not mention when to prefer this tool over siblings such as score_due_claims or score_thesis_outcome, so alternatives are not addressed.

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