Valuein — SEC EDGAR Fundamentals & Smart-Money Data

List My Research Reports

list_my_reports

Read-onlyIdempotent

Cursor-paginated newest-first listing of the caller's own reports (owner-scoped). Filters compose with AND; status defaults to 'ready' so pass status='draft' or 'all' to see drafts. Use cursor from the previous response's next_cursor to fetch the next page (limit max 100). Sample tier rejected (no per-author state).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Page size.
`cursor`	No	Cursor from previous `next_cursor`.
`status`	No	Filter by status. Default 'ready' (excludes drafts + delisted).	ready
`ticker`	No	Filter to a single ticker (case-insensitive).
`report_type`	No	Filter by report type.

Output Schema

TableJSON Schema

Name	Required	Description
`_meta`	Yes	Provenance envelope — data lineage for every MCP response
`reports`	Yes
`next_cursor`	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 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"
```
AddedMay 12, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context beyond annotations: pagination is cursor-based and newest-first, filters compose with AND, status defaults to 'ready' (excluding drafts and delisted), and the sample tier is rejected due to no per-author state. It does not describe the output shape, but an output schema exists, so that is not required. The only minor gap is not explicitly stating that the listing is read-only, but annotations cover that.

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 sentences, each earning its place. The first sentence states the core purpose and scope. The second provides filter semantics and the critical status default. The third explains pagination and the sample tier limitation. No filler, no repetition of schema details, and the most important information (owner-scoped, newest-first, status default) is front-loaded.

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 read-only listing tool with an output schema, 100% parameter coverage, and annotations covering safety, the description is complete. It covers pagination mechanics, filter composition, status defaults, and a known environmental limitation (sample tier rejection). An agent has everything needed to invoke this tool correctly: which parameters to pass, how to paginate, and what to expect in terms of scope. The output schema handles return-value documentation, so no gap exists there.

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 description coverage is 100%, so the schema already documents all five parameters. The description adds meaningful semantic context beyond the schema: it explains that filters compose with AND, that status defaults to 'ready' and why (to exclude drafts), and that cursor should come from the previous response's next_cursor. It also clarifies the limit max of 100, which is in the schema but reinforced. The description does not repeat parameter names but adds behavioral meaning to them, which is exactly what this dimension rewards.

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 ('listing'), a specific resource ('the caller's own reports'), and a clear scope ('owner-scoped'). It also distinguishes itself from sibling tools like search_reports and list_report_versions by emphasizing owner-scoping and pagination. The title 'List My Research Reports' reinforces the owner-scoped purpose, making it easy for an agent to select this tool over 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?

The description explicitly explains when to use this tool: to list the caller's own reports, with filters composing via AND. It also provides critical usage guidance: status defaults to 'ready', so pass status='draft' or 'all' to see drafts; use cursor from previous next_cursor for pagination; limit max 100. It even notes the sample tier rejection due to no per-author state, which helps an agent understand when this tool may not be available. This is explicit when-to-use guidance with no ambiguity.

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.