Skip to main content
Glama
putervision

world-model-mcp

by putervision
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

manage_snapshot

Destructive

Save, restore, diff, undo, list, or time-travel a spatial world database. Use it to roll back or compare world state instead of editing single entities.

Instructions

Checkpoint, diff, undo, or time-travel the spatial world database. Actions: save, restore, diff, list, undo, history, time_travel. restore (overwrites live state) and undo (reverts last matching mutation) are destructive and not always reversible except by saving first. diff, list, history, and time_travel are read-only. Returns {ok, action, snapshots[]|diff|state}. Use manage_snapshot instead of update_entity when rolling back, diffing, or time-traveling database state rather than editing single entities.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoSnapshot name for save/restore
typeNoMutation type to undo (default: any)
actionNoAction to perform (default: list)
projectNoOptional project identifier
entity_idNoTarget entity ID for undo or history lookup
timestampNoISO timestamp for time-travel reconstruction
snapshot_aNoFirst snapshot name for diff
snapshot_bNoSecond snapshot name for diff
descriptionNoOptional snapshot description

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.1
    • addedInput schema / properties / action / enum
      Added value: +[
+  "save",
+  "restore",
+  "diff",
+  "list",
+  "undo",
+  "history",
+  "time_travel"
+]
  2. Changed3 schema fields changedv0.4.1
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / action / enum
      Removed value: -[
-  "save",
-  "restore",
-  "diff",
-  "list",
-  "undo",
-  "history",
-  "time_travel"
-]
  3. First observedv0.3.1

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing per-action behavior: restore overwrites live state, undo reverts the last matching mutation, and both are 'not always reversible except by saving first,' while diff/list/history/time_travel are read-only. The annotations only give tool-level destructive/idempotent hints; the description gives action-level detail that is exactly what an agent needs to avoid data loss.

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?

Front-loaded with the verb set, then actions, then safety warnings, then return shape, then sibling routing — every sentence carries distinct information with no padding.

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?

For a 7-action tool with no output schema and no required params, the description supplies the action taxonomy, destructive/read-only classification, return envelope ({ok, action, snapshots[]|diff|state}), and routing versus siblings. 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.

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds action semantics and defaults ('type' is the mutation type to undo, default any) and maps parameters to actions (name for save/restore, timestamp for reconstruction). It adds meaning beyond the field-level descriptions without fully restating them.

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?

Opens with a specific verb set ('Checkpoint, diff, undo, or time-travel') and resource ('spatial world database'), then enumerates the exact action enum. It explicitly distinguishes itself from the sibling update_entity, so an agent can route without opening either schema.

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?

States when to use it versus a named alternative: 'Use manage_snapshot instead of update_entity when rolling back, diffing, or time-traveling database state rather than editing single entities.' It also flags which actions are destructive, giving both when-to-use and when-to-be-careful guidance.

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

Deploy Server

Other Tools