Skip to main content
Glama

list_snapshots

Read-only

Lists saved snapshots in a Roblox place—name, class, descendant count, and restore path—so you can get the exact name before restoring or deleting one. Read-only.

Instructions

List the snapshots saved in this place: name, class, descendant count and the path each one restores to. Read-only. Call it before restore or delete_snapshot to get the exact name; returns "(no snapshots)" when there are none.

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
placeNoTarget place (PlaceId or project name). Defaults to the bound/sole connected place.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description is consistent with that ('Read-only'). It adds genuine behavioral context beyond the annotations: the exact field set returned and the literal empty-state string '(no snapshots)', which helps the agent recognize a no-op result. It stops short of covering ordering, pagination, or cost, so it is not a full 5.

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, front-loaded with the resource and its returned fields, then the routing rule and the empty-state marker. Every clause carries information; nothing is padded.

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

Completeness5/5

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

There is no output schema, so the description must carry the return-value burden, and it does by naming the fields and the empty-result string. With one optional parameter fully covered by the schema and annotations covering safety, nothing an agent needs to invoke it correctly is missing.

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?

Schema description coverage is 100%, and the single 'place' parameter is already documented in the schema as a PlaceId or project name defaulting to the bound/sole place. The description adds nothing about the parameter beyond that, so the baseline 3 applies.

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?

States a specific verb and resource ('List the snapshots saved in this place') and enumerates the returned fields (name, class, descendant count, restore path), so the agent knows exactly what comes back. It also distinguishes itself from siblings by naming restore and delete_snapshot as consumers of this output.

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?

Gives an explicit when-to-use rule: 'Call it before restore or delete_snapshot to get the exact name.' That ties invocation to concrete downstream tools rather than leaving the agent to infer why it would list snapshots.

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