Skip to main content
Glama
putervision

state-memory-mcp

by putervision
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

manage_snapshots

Destructive

Create, list, diff, revert, and undo workflow state checkpoints to compare versions, recover historical graph states, and track node audit history.

Instructions

State checkpointing, time travel, diffing, and undo operations (actions: save, list, diff, get_state, revert, undo, get_history). Use manage_snapshots instead of manage_database when reverting state graph mutations or comparing checkpoints rather than physical database file maintenance.

Returns snapshot record, state graph diff, historical graph state, or node audit history.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
forceNoForce snapshot even if node count is high.
limitNoMaximum snapshots to list (1-1000).
actionYesThe snapshot management action to execute: save, list, diff, get_state, revert, undo, get_history.
node_idNoNode ID for undo or get_history.
projectNoTarget project name or slug.
timestampNoISO 8601 timestamp for get_state or revert.
session_idNoOptional session identifier for save.
snapshot_id_aNoFirst snapshot ID for diff.
snapshot_id_bNoSecond snapshot ID for diff.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.1
    • changedInput schema / properties / action / description
      Previous value: -"The snapshot management action to execute."New value: +"The snapshot management action to execute: save, list, diff, get_state, revert, undo, get_history."
    • addedInput schema / properties / action / enum
      Added value: +[
+  "save",
+  "list",
+  "diff",
+  "get_state",
+  "revert",
+  "undo",
+  "get_history"
+]
  2. Changed3 schema fields changedv1.2.1
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -true
    • addedInput schema / required
      Added value: +[
+  "action"
+]
  3. Addedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered. The description adds return types but never clarifies that revert/undo mutate state while list/diff/get_state/get_history are safe reads, leaving mixed-action risk unstated.

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 tight paragraphs with the core capability front-loaded before the alternative and the return summary. The parenthetical action list is mildly redundant with the schema enum, but no sentence is wasted.

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 nine-parameter, seven-action tool with no output schema, the description supplies purpose, differentiation, action inventory, and return types, which is substantial. It lacks per-action parameter applicability (e.g., timestamp for get_state/revert), the one remaining gap for a tool this complex.

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 each parameter is documented, so the burden is on the schema. The description's restatement of the action list duplicates the enum and adds no mapping of which parameters apply to which action.

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 specific verbs and resources (state checkpointing, time travel, diffing, undo) and enumerates the supported actions, so an agent knows exactly what domain this covers. It explicitly distinguishes itself from the sibling manage_database, making it separable without opening the schema.

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?

Explicitly routes the agent away from manage_database with a concrete condition: use this when reverting state graph mutations or comparing checkpoints rather than physical database file maintenance. It does not advise when to pick among the seven internal actions or when not to snapshot at all, so it stops short of a full 5.

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