Skip to main content
Glama

mnemon_reconcile_schema

Reconcile schemas across source, target, and ephemeral branches, then run a migration dry-run before merging to catch conflicts early.

Instructions

Perform 3-way schema reconciliation and migration dry-run before merging an ephemeral branch into target.

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": "<branch>"
    },
    "name": "mnemon_reconcile_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
branchYesSource branch identifier to reconcile
tenant_idYesDatabase tenant identifier
target_branchNoTarget branch to reconcile against (default: main)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. The phrase 'dry-run' usefully signals no changes are applied, which is meaningful for a migration-adjacent tool, but it says nothing about output format, failure modes, permission requirements, or what '3-way' compares against. That leaves meaningful behavioral gaps for an unannotated 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 sentence with zero filler, and the key action and the precondition are front-loaded. Nothing is repeated or padded.

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 tool with no annotations and no output schema, the definition should say what the dry-run returns, such as a diff report or migration plan, and whether it is purely non-mutating. Those gaps matter for an agent deciding whether to run it and how to interpret the result, though the parameters and workflow position are otherwise well covered.

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 all three parameters are already documented, including the default target_branch of main. The description only adds context by implying three participants (source branch, target branch, and an implicit common ancestor), which is modest added meaning 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 set (3-way schema reconciliation plus migration dry-run) and a concrete resource (schema), and it scopes the operation to merging an ephemeral branch into a target. It is clearly distinguishable from simple reads like mnemon_get_schema or mnemon_diff_branch, though no sibling is named explicitly to sharpen that contrast.

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

Usage Guidelines4/5

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

It states a clear usage context: run this before merging an ephemeral branch into the target, which tells the agent where in a workflow it belongs. It stops short of naming alternatives (e.g., diff_branch) or stating when not to use it, so it is not a full 5.

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