Skip to main content
Glama

mnemon_promote_branch

Promote a preview or ephemeral database branch to primary production root with an atomic pointer swap for zero-downtime cutover.

Instructions

Promote a preview/ephemeral database branch to primary production root with atomic zero-downtime pointer swap.

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_promote_branch"
  }
}

Input Schema

NameRequiredDescriptionDefault
branch_idYesBranch ID to promote to primary root
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?

With no annotations, the description carries the full burden. It usefully discloses that the swap is atomic and zero-downtime, which is real behavioral value, but says nothing about what happens to the existing primary, whether the change is reversible, or what permissions/tenant state 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 front-loaded sentence with the destructive, production-affecting action stated first and no filler. Every clause (preview/ephemeral, primary production root, atomic, zero-downtime) contributes information.

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?

For a production-affecting mutation with no annotations and no output schema, the definition covers the core mechanics but omits the consequential details an agent needs: irreversibility/rollback, fate of the demoted primary, and required authorization. Adequate but with clear gaps.

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% (both required params documented), so the schema already explains branch_id and tenant_id. The description adds no format, constraint, or identifier-resolution detail beyond it, making the baseline 3 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?

States a specific verb (promote), a specific resource (preview/ephemeral branch), and the exact target state (primary production root), plus the mechanism (atomic pointer swap). This is enough to distinguish it from create/reset/diff/lineage siblings without opening their schemas.

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?

No explicit when-to-use or when-not-to-use guidance, no prerequisites, and no mention of how it relates to alternatives such as thanaton_promote or mnemon_import_cutover. The agent must infer that this is the 'go live' step from the purpose sentence 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