tentra

list_snapshots

Retrieve indexed snapshots for a repository to enable time-travel comparisons and identify differences between versions.

Instructions

List all indexed snapshots for a repo, newest first. Use for time-travel — pick two snapshot IDs and call diff_snapshots.

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": {
      "repo_id": "<repo_id>"
    },
    "name": "list_snapshots"
  }
}

Input Schema

Name	Required	Description	Default
`repo_id`	Yes	Repo ID to list snapshots for

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Apr 18, 2026

TDQS

A4.4/5.0

Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses the sorting order ('newest first') and hints at the tool's role in a workflow ('time-travel'), but lacks details on permissions, rate limits, or output format. It doesn't contradict annotations since none exist.

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 with zero waste: the first states purpose and behavior, the second provides usage guidance. It's front-loaded with essential information and appropriately sized for the tool's complexity.

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 tool's low complexity (1 parameter, no annotations, no output schema), the description is largely complete. It covers purpose, usage, and behavioral context, though it could benefit from mentioning output structure or error handling for full completeness.

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 fully documents the single parameter. The description adds no parameter-specific details beyond what the schema provides, but with 0 parameters needing semantic clarification (only 1 parameter fully covered), this meets a high baseline.

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 clearly states the verb ('List') and resource ('all indexed snapshots for a repo') with specific scope ('newest first'). It distinguishes from sibling tools like 'diff_snapshots' by focusing on listing rather than comparing.

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?

Explicitly states when to use ('Use for time-travel') and provides a clear alternative ('pick two snapshot IDs and call diff_snapshots'), directly naming the sibling tool for comparison operations.

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