Valuein — SEC EDGAR Fundamentals & Smart-Money Data

List Claims for Thesis

list_claims_for_thesis

Read-onlyIdempotent

List the claims composing a thesis, each with its role (supports/refutes/context). This is how you read a thesis as the structured argument it is — its supporting and disconfirming claims with their current statuses. Archived claims are omitted. Tier: paid + free (sample rejected).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`thesis_id`	Yes	Id of the thesis whose claims to list.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`_meta`	Yes	Provenance envelope — data lineage for every MCP response
`items`	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 / items / items / 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 / items / items / 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

changed

Output schema / properties / items / items / 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

A4.1/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds genuinely useful behavioral context beyond those annotations: archived claims are omitted, claims are returned with roles and current statuses, and a tier restriction (paid + free, sample rejected) is disclosed. No contradiction exists.

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?

The description is three tight sentences with the core action front-loaded. Every sentence adds information: the resource and role, the intended reading purpose, and the archived/tier caveats. No redundant filler or restatement of the tool name.

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?

For a single-parameter, read-only list tool with full schema coverage and an output schema, the description is complete. It clarifies what is included (claims, roles, statuses), what is excluded (archived claims), and access constraints (tier). No critical operational detail needed to call it correctly 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%; the single parameter thesis_id is already documented in the schema as 'Id of the thesis whose claims to list.' The description adds no additional parameter-level semantics, so the baseline score of 3 is appropriate.

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?

The description states a specific verb and resource: it lists the claims composing a thesis, distinguishing this from the more general sibling list_claims by emphasizing the thesis-argument structure and role (supports/refutes/context). The sentence 'This is how you read a thesis as the structured argument it is' reinforces the intended semantic scope.

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 implies when to use the tool ('This is how you read a thesis...'), but it does not explicitly name alternatives such as list_claims or get_thesis, nor does it state when NOT to use it. Archived claims are mentioned as excluded, but no routing between sibling tools is provided.

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.