Skip to main content
Glama
legacy-switch-mcp

legacy-switch-mcp

list_snapshots

List saved switch state files for a given switch or all switches, including backups and pre-apply snapshots, newest first, to identify rollback points before applying changes.

Instructions

Saved state files (backups and the snapshot before every apply), newest first.

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_snapshots"
  }
}

Input Schema

NameRequiredDescriptionDefault
switchNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/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 the full burden. It usefully discloses result ordering (newest first) and the composition of the listed set, and the listing nature implies it is read-only. It says nothing about pagination, result volume, or permissions, which matter for a snapshot listing that could be large.

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?

One short, front-loaded sentence fragment with zero filler; the most important information (what is listed, ordering) comes first. It is a fragment rather than a full clause, which is a minor stylistic cost but no loss of content.

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?

An output schema exists, so return-value detail is not required. The description covers what the tool returns and in what order, which is adequate for a simple read, but it leaves the one parameter undocumented and gives no guidance on the surrounding tool choices.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single optional parameter, switch, has 0% schema description coverage, and the description never mentions it. The agent cannot tell from either source whether switch filters the listing to one device or selects something else, leaving the only parameter semantically opaque.

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?

The description names the concrete resource: saved state files, and specifies what they include (backups plus the pre-apply snapshot) and their ordering (newest first). That is more informative than the name alone. It does not, however, distinguish this tool from siblings that look adjacent (list_files, backup_state, get_state), so an agent must infer the boundary.

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

Usage Guidelines2/5

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

There is no explicit statement of when to use this tool versus list_files, backup_state, or get_state, and no stated prerequisites or exclusions. The parenthetical about 'the snapshot before every apply' implies a restore or audit use case, but the agent must infer it.

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