Skip to main content
Glama

mnemon_time_travel

Read database branch state at a specific historical timestamp or WAL LSN via PostgreSQL continuous WAL replay, instantiating a target branch for point-in-time recovery or debugging.

Instructions

Read database branch state at a specific historical point in time (timestamp or LSN) via PostgreSQL continuous WAL replay.

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": {
      "tenant_id": "<tenant_id>"
    },
    "name": "mnemon_time_travel"
  }
}

Input Schema

NameRequiredDescriptionDefault
tenant_idYesDatabase tenant identifier
target_lsnNoNumeric WAL Log Sequence Number
target_timeNoISO 8601 target timestamp (e.g., 2026-11-15T01:00:00Z)
target_branchNoTarget branch name to instantiate (default: time-travel)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it omits key traits. The schema's target_branch parameter ('Target branch name to instantiate') implies a write side effect, which sits awkwardly with the description's framing of the operation as a read; cost/latency of WAL replay, permissions, and reversibility are also undisclosed.

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?

A single well-formed sentence, front-loaded with the core verb and resource, with the mechanism and the two accepted input modes appended compactly. No filler to remove.

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

Completeness2/5

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

For a 4-parameter tool with no annotations and no output schema, the description should explain the return shape (what 'branch state' means as output) and the branch-instantiation side effect. Neither is addressed, so an agent cannot predict what it gets back or whether a branch is created.

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%, so the primary documentation burden is met by the schema; the description only reinforces the target_time/target_lsn addressing modes. It does not clarify whether target_lsn and target_time are mutually exclusive or how target_branch interacts with the read semantics, so it adds little beyond the schema.

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 (read) and resource (branch state at a historical point) and names the mechanism (continuous WAL replay) plus the two addressing modes (timestamp or LSN). It does not distinguish itself from close siblings like mnemon_pitr_restore, mnemon_wal_rewind, or mnemon_create_branch, which is the remaining gap for a 5.

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?

The description implies when the tool applies — querying historical state at a timestamp or LSN — but never says when to prefer it over mnemon_pitr_restore, mnemon_pitr_timelines, or mnemon_wal_rewind. No exclusions or prerequisites are given, so the agent must infer the boundary from sibling names alone.

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