Skip to main content
Glama

mnemon_pitr_restore

Restore a database cluster to a historical LSN or timestamp on a new branch to recover point-in-time state without altering the original branch.

Instructions

Restore a database cluster to a historical LSN or timestamp on a new branch.

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>",
      "target_branch": "<target_branch>"
    },
    "name": "mnemon_pitr_restore"
  }
}

Input Schema

NameRequiredDescriptionDefault
tenant_idYesDatabase tenant identifier
target_lsnNoTarget WAL Log Sequence Number
target_branchYesName of new branch for restored state

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

B3.2/5.0
Behavior3/5

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

With zero annotations, the description carries the full behavioral burden; it does disclose the key trait that the restore lands on a NEW branch, implying the existing cluster is untouched, which is genuinely useful. However it says nothing about required permissions, whether the branch must not already exist, restore duration/blocking, or what happens on failure. It also mentions 'timestamp' even though no timestamp parameter exists in the schema, which muddies the contract.

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?

A single front-loaded sentence with no filler or repetition. It is efficient, though arguably too terse for a point-in-time restore operation, and the phrase 'LSN or timestamp' is imprecise against the actual schema.

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

Completeness3/5

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

The core action and destination are clear, and the schema fills in the parameter contracts, but for a high-impact restore operation with no annotations and no output schema the definition omits prerequisites, return value (presumably new branch details), and side effects. The timestamp/LSN mismatch is the main unresolved gap.

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 all three parameters are already documented, and the baseline is 3; the description only restates that the target is a historical LSN/timestamp and the branch is new. The timestamp reference adds confusion rather than meaning, since the schema exposes only target_lsn as a numeric point-in-time selector.

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?

Names a specific verb (Restore), resource (database cluster), and scope (to a historical LSN/timestamp onto a new branch), which distinguishes it from read-only siblings like mnemon_time_travel or mnemon_wal_rewind. It never names those alternatives explicitly, so the differentiation is inferable rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no named alternative among the many closely related siblings (time_travel, wal_rewind, create_branch, promote_branch). The phrase 'on a new branch' hints at non-destructive restore semantics, but the agent must infer all routing decisions.

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