instabox-mcp

List snapshots

instabox_list_snapshots

Read-onlyIdempotent

Lists saved machine snapshots (software and /data files) oldest first, helping you choose a baseline for starting new machines.

Instructions

List your snapshots, oldest first. A snapshot is a saved copy of a machine's software and /data files (not memory or processes); new machines can start from it.

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": "instabox_list_snapshots"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 1, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile needs no restating. The description instead adds domain semantics the annotations can't: what a snapshot contains (software and /data, not memory or processes) and that new machines can start from it. It stops short of describing pagination or result shape.

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 with the action and ordering front-loaded and the definition following as supporting context. Nothing is repeated from the annotations and no sentence is filler.

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 zero-parameter, read-only list tool with no output schema, the description covers the action, ordering and the meaning of the returned entity. Return fields are the only remaining gap, and they are largely implied by the snapshot definition.

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?

The tool takes zero parameters, so the schema has nothing to explain and the baseline is 4. The description correctly spends no words on parameter syntax and instead uses the space for domain context.

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 your snapshots') plus the ordering ('oldest first'), which is enough for an agent to distinguish it from instabox_get_snapshot (single item). It doesn't explicitly point to the sibling for details, so full sibling differentiation 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 Guidelines3/5

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

Usage is only implied by 'list your snapshots' – there is no stated when-to-use or when-not, and no reference to instabox_get_snapshot or instabox_list_snapshot_files as alternatives. The 'oldest first' ordering gives some selection context but no routing guidance.

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