Skip to main content
Glama

mnemon_diff_branch

Inspect SQL DDL schema differences and migration scripts between a branch and its parent to plan safe database changes.

Instructions

Inspect SQL DDL schema diff and migration script between a branch and its parent.

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

Input Schema

NameRequiredDescriptionDefault
branch_idYesBranch ID to diff
tenant_idYesDatabase tenant identifier
parent_branchNoParent branch (default: 'main')

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. 'Inspect' signals a read-only operation and the text usefully discloses that the result includes both a DDL diff and a migration script, but it says nothing about permissions, whether the script is generated or stored, or which direction the diff runs (branch vs. parent).

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 no filler; the verb, the artifact type, and the comparison scope all land immediately.

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?

With no annotations and no output schema, the description would need to explain the return shape, but it names only the two artifacts (diff, migration script) without saying how they are presented or whether the output is ordered by object. Adequate for a simple read tool, but leaves real 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%, so all three parameters (branch_id, tenant_id, parent_branch with its 'main' default) are already documented in the schema. The description adds only the conceptual relationship being compared and nothing about parameter formats or edge cases, so the baseline 3 applies.

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 ('Inspect') and a precise resource ('SQL DDL schema diff and migration script') scoped to 'between a branch and its parent'. That scope distinguishes it implicitly from sibling tools like mnemon_get_schema (current schema) and mnemon_reconcile_schema, though no sibling is named.

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: an agent can infer this is for comparing a branch's schema against its parent, presumably before promoting or reconciling. There is no explicit when-to-use statement, no exclusions, and no pointer to an alternative tool for related schema tasks.

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