Skip to main content
Glama
huaidj-rufus

huaidj-rufus

by huaidj

list_export_snapshots

Read-onlyIdempotent

List local versioned export-metadata snapshot summaries by date and exporter version to select a backup for restore preview without rehashing all backups.

Instructions

List local versioned export-metadata snapshot summaries by date and declared exporter version. This bounded summary listing does not rehash all backups and does not establish database integrity; restore preview still validates the complete snapshot.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_export_snapshots"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds useful scope ('local', 'versioned', 'bounded', does not rehash backups or assert integrity), but does not describe the shape of a summary entry or ordering/pagination behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, purpose front-loaded, and the second sentence enumerates the tool's limits rather than padding. Phrasing like 'does not rehash all backups' is slightly jargony but carries real information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and no parameters, the description should describe what a returned 'summary' contains (fields, ordering, count). It covers scope and caveats well but leaves the return payload opaque, which matters more here because there is no output schema to fall back on.

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?

Zero parameters, which normally sets a baseline of 4, but the description's mention of 'by date and declared exporter version' hints at grouping dimensions that are not actually selectable inputs. With no schema fields to disambiguate, it adds only minimal semantic value.

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?

Specific verb and resource: 'List local versioned export-metadata snapshot summaries', scoped to date and declared exporter version. It is clearly bounded against rehashing backups, though it does not name the sibling tools it contrasts with, relying on the role phrase 'restore preview' instead.

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?

Explicit negative guidance routes the agent: this listing 'does not establish database integrity; restore preview still validates the complete snapshot', implying use this for cheap listing and the preview tool for validation. It stops short of an explicit 'use this when' clause or naming preview_export_snapshot / preview_export_restore directly.

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