Skip to main content
Glama

list_report_versions

Read-onlyIdempotent

List a report's saved versions, newest first (version, when, who, source tool, summary, restoredFrom). Use when choosing a version to restore with restore_report_version.

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": {
      "reportId": "<reportId>"
    },
    "name": "list_report_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
reportIdYesReport id

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered and nothing in the description contradicts it. The description adds real context by declaring the sort order and the returned fields (version, when, who, source tool, summary, restoredFrom). It does not mention pagination or limits, which matters for a list tool with no output schema.

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 tight sentences, front-loaded with the action and ordering, then the return fields, then the routing hint. Every clause carries information and none is redundant.

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 one-parameter read tool with no output schema, listing the return fields and sort order gives the agent a usable mental model of the response. The only real omission is volume/pagination behavior, which is minor given the annotation-covered safety profile.

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?

There is a single required parameter with 100% schema description coverage, so the schema carries the burden. The description says 'a report's saved versions,' which merely confirms reportId is the scoping key, adding no syntax or format detail. Baseline 3 is appropriate.

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?

States a specific verb and resource ('List a report's saved versions') plus the ordering ('newest first') and the fields returned. It clearly separates listing from the restore action it feeds, though the differentiation from siblings like get_report is only implied.

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 says when to use it: 'Use when choosing a version to restore with restore_report_version,' naming the companion tool. It gives no when-not guidance or prerequisites (e.g., permissions, what happens if the report has no versions), so it falls short of full routing coverage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources