Skip to main content
Glama

mnemon_reset_branch

Reset an ephemeral database branch to its parent snapshot in under 50ms, wiping all test mutations so you can reuse the branch for clean tests.

Instructions

Reset an ephemeral database branch back to its parent snapshot in <50ms, wiping all test mutations.

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>",
      "branch_id": "<branch_id>"
    },
    "name": "mnemon_reset_branch"
  }
}

Input Schema

NameRequiredDescriptionDefault
branch_idYesBranch ID to reset
tenant_idYesDatabase tenant identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose the key behavioral trait: this is destructive and wipes all mutations on the branch. It also advertises latency (<50ms). It omits whether the wipe is recoverable, whether concurrent sessions/queries are affected, whether the parent branch is untouched, and what permissions are required.

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 tightly packed sentence with the destructive effect front-loaded alongside the operation and its performance characteristic. No filler, nothing redundant.

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?

Both required parameters are fully documented in the schema and there is no output schema, so the description need only carry purpose and behavior. For a destructive operation with zero annotations, ideally it would also clarify recoverability and blast radius (only this branch, parent unaffected) and state what a caller gets back.

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%, with both tenant_id and branch_id documented in the schema, so the baseline is 3. The description adds no syntax, format, or scoping detail about either parameter beyond what the schema already provides.

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 and resource ("Reset an ephemeral database branch") plus the target state ("back to its parent snapshot"), so the operation is unambiguous. It does not name or differentiate from potentially overlapping siblings such as time_travel or pitr_restore, which is the only thing keeping it from 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 phrases "ephemeral" and "wiping all test mutations" imply a test-workflow reset scenario, which gives an agent indirect guidance on when this applies. However, there is no explicit when-to-use vs. when-not, and no mention of the alternatives (e.g., point-in-time restore or time travel) that could accomplish similar recovery goals.

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