Skip to main content
Glama
Sign In

Valuein — SEC EDGAR Fundamentals & Smart-Money Data

by biz.valuein
OverviewDiscussionsAdmin

List Report Versions

list_report_versions
Read-onlyIdempotent

Author-only newest-first listing of a report's archived version history. Each entry summarises what changed (sections edited, etc.) so the workspace UI can render a clickable history without loading every artifact. Pair with get_report_version to fetch a specific version's content for diffing against HEAD.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "report_id": "<report_id>"
    },
    "name": "list_report_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of archived versions to return (1–100). Defaults to 20.
cursorNoCursor from the previous response's `next_cursor` — the smallest version number on the previous page. Omit for the first page.
report_idYesIdentifier of the report whose version history to list, as returned by create_report or list_my_reports.

Output Schema

NameRequiredDescriptionDefault
_metaYesProvenance envelope — data lineage for every MCP response
versionsYes
next_cursorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedOutput schema / properties / _meta / properties / price_as_of
      Removed value: -{
-  "description": "ISO timestamp when the price surfaces were last refreshed.",
-  "type": "string"
-}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behaviour: author-only access gating, descending version ordering, and that entries are lightweight summaries rather than full artifacts. It does not mention rate limits or what happens on an invalid cursor, but the bar is lower given full annotation coverage.

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?

Two sentences, zero filler, with the access scope and ordering front-loaded before the purpose and the sibling pairing. Every clause carries information an agent can act on.

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 three-parameter read tool with full annotation coverage and an output schema, the description covers scope, ordering, entry granularity and composition with a sibling. Only minor gaps remain, such as pagination behaviour when results exceed the limit, which the schema partly implies.

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 limit, cursor and report_id are all documented in the schema itself, including the cursor's 'smallest version number on the previous page' semantics. The description adds only the implied 'newest-first' ordering, which aligns with the cursor definition but supplies no additional format or constraint detail. Baseline 3 applies.

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?

Names a specific verb and resource ('listing of a report's archived version history') and adds two distinguishing qualifiers: 'Author-only' and 'newest-first'. The closing purpose clause (render a clickable history without loading every artifact) makes it unmistakable against the sibling get_report_version.

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

Usage Guidelines4/5

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

Explicitly routes the agent: 'Pair with get_report_version to fetch a specific version's content for diffing against HEAD', which sets a clear division of labour. It also signals an access precondition ('Author-only'). It stops short of stating when NOT to call it or what happens for non-authors.

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