Skip to main content
Glama

mnemon_create_branch

Fork a copy-on-write PostgreSQL database branch at an exact WAL LSN without storage duplication, optionally masking PII for compliance.

Instructions

Fork an instant copy-on-write PostgreSQL database branch in 31ms at an exact WAL LSN without storage duplication.

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>",
      "new_branch": "<new_branch>"
    },
    "name": "mnemon_create_branch"
  }
}

Input Schema

NameRequiredDescriptionDefault
mask_piiNoMask sensitive PII columns in child branch for GDPR/HIPAA compliance
tenant_idYesDatabase tenant/cluster identifier
new_branchYesName for the new branch (e.g. 'feature-migration')
target_lsnNoOptional WAL LSN for point-in-time fork
parent_branchNoParent branch name (default: 'main')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.7
    • addedInput schema / properties / mask_pii
      Added value: +{
      +  "description": "Mask sensitive PII columns in child branch for GDPR/HIPAA compliance",
      +  "type": "boolean"
      +}
  2. First observedv1.0.6

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It does disclose valuable traits — copy-on-write semantics, no storage duplication, 31ms latency, LSN-exact forking — but says nothing about permissions required, whether the parent branch is affected, or what the call returns. It is above a bare restatement but far from a complete behavioral picture for a mutation tool.

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 tight sentence with the action front-loaded and no filler. Every clause (copy-on-write, 31ms, exact LSN, no duplication) conveys a distinct, useful property.

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 schema is fully documented and there is no output schema, so the description's main unmet needs are usage routing and mutation side effects. For a 5-parameter branch-creation tool with no annotations, the definition is adequate but leaves the agent to guess at alternatives and blast radius.

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%, so every parameter is already documented, making 3 the baseline. The description adds only marginal meaning, clarifying that target_lsn enables point-in-time forking; it says nothing about mask_pii or parent_branch 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 ('Fork') and a specific resource ('PostgreSQL database branch'), plus differentiating traits (copy-on-write, 31ms, exact WAL LSN). An agent can tell this creates a branch, but the description never names or distinguishes it from siblings like mnemon_create_snapshot or mnemon_pitr_restore, which likely overlap conceptually.

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 explicit when-to-use or when-not-to-use guidance, and no alternative tool is named. An agent must infer from the phrase 'fork a branch' that this is for creating writable derived environments rather than snapshots or point-in-time restores, which is a meaningful inference across several overlapping siblings.

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