Skip to main content
Glama
Sign In
Mnemograph

Mnemograph

by tm42
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

restore_state_at

Restore the knowledge graph to a prior state by timestamp. Preview changes with get_state_at, then execute to preserve a full audit trail.

Instructions

Restore graph to state at a specific timestamp. Emits clear + recreate events — full audit trail preserved. Use get_state_at() first to preview what will be restored.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "timestamp": "<timestamp>"
    },
    "name": "restore_state_at"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoWhy restoring (recorded in events)
timestampYesISO datetime or relative ('2 hours ago', 'yesterday')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A4.4/5.0
Behavior4/5

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

No annotations provided, but the description discloses that the tool 'Emits clear + recreate events' and mentions 'full audit trail preserved,' giving insight into side effects and logging behavior.

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 concise sentences covering purpose, behavior, and guidance; no extraneous content.

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?

Given no output schema, the description sufficiently explains the tool's behavior and audit trail preservation. Could mention return value or error cases, but overall complete enough for an agent.

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 coverage is 100% (both parameters described in schema). The description echoes schema info without adding new meaning; baseline 3 is appropriate.

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?

Description clearly states the action: 'Restore graph to state at a specific timestamp.' It also distinguishes from sibling tools like 'get_state_at' by recommending previewing first, and from 'rewind' by specifying events emitted.

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?

Explicitly advises using 'get_state_at() first to preview what will be restored,' providing clear guidance on when to use this tool vs. an alternative.

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