Skip to main content
Glama

mnemon_merge_branch

Fast-forward merge schema changes and table additions from a staging or feature branch back into the parent trunk branch.

Instructions

Fast-forward merge schema modifications and table additions from a staging/feature branch back to parent trunk in <200ms.

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

Input Schema

NameRequiredDescriptionDefault
branch_idYesBranch ID containing changes to merge
tenant_idYesDatabase tenant identifier
parent_branchNoParent target branch (default: 'main')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.7

TDQS

A3.6/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. It does add genuine behavioral content beyond the schema: the merge is fast-forward only (implying it fails on divergence) and completes in <200ms. However, it is silent on what happens on conflict, whether the source branch is consumed or left intact, permissions/auth requirements, and reversibility of a schema mutation.

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 action, direction, and latency claim; nothing is redundant or buried, and it can be read in one pass.

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

Completeness4/5

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

For a three-parameter tool with full schema coverage and no output schema, the definition is close to sufficient: it tells the agent what moves and where. The remaining gap is the failure mode (non-fast-forward / conflict handling) and post-merge state of the source branch, which matter for a mutation with no annotations to fall back on.

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 the parameters are already documented individually, including the 'main' default for parent_branch. The description reinforces the direction of the mapping (branch_id is the source, parent_branch the target) but adds no new syntax, format, or constraint information 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?

The description gives a specific verb (fast-forward merge) plus the exact resources moved (schema modifications and table additions) and the direction (staging/feature branch back to parent trunk). It is clearly distinguishable from read-only siblings like mnemon_diff_branch or mnemon_branch_lineage, but it never differentiates itself from likely-overlapping siblings such as mnemon_promote_branch or mnemon_reconcile_schema.

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?

Usage is only implied: the phrase 'staging/feature branch back to parent trunk' signals the scenario, and 'fast-forward' implies the prerequisite that the parent has not diverged. There is no explicit when-to-use, no when-not-to-use, and no named alternative for the case where a fast-forward is not possible.

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