Skip to main content
Glama

mnemon_import_cutover

Execute a zero-downtime cutover that routes all connection pool traffic to Mnemon-DB by tenant ID, completing database imports without dropping active connections.

Instructions

Execute zero-downtime cutover, routing all connection pool traffic to Mnemon-DB.

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

Input Schema

NameRequiredDescriptionDefault
tenant_idYesDatabase tenant identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It asserts a "zero-downtime" property but says nothing about irreversibility, rollback path, permissions required, whether existing connections are drained, what happens on failure mid-cutover, or whether the operation is idempotent — critical omissions for a traffic-routing switch.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence naming the action and its outcome, with no filler. It is efficient, though its brevity borders on under-specification given the operation's risk.

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

Completeness2/5

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

For a high-impact traffic cutover with no annotations and no output schema, the description is too thin: no preconditions, failure semantics, post-cutover state, or verification step. An agent could not safely decide whether calling it is reversible or what to do if it half-succeeds.

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 coverage is 100% with a single documented parameter (tenant_id), so the schema already does the work. The description adds no extra meaning about what the tenant scopes — e.g. whether it is the source being cut over to Mnemon-DB or the target context.

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 ("Execute zero-downtime cutover") and the concrete effect ("routing all connection pool traffic to Mnemon-DB"), which is distinct from import/status siblings. It does not name the sibling it supersedes or must follow, so an agent has to infer the migration-phase relationship.

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, no mention of prerequisites (e.g. that an import must have completed, or that status should be checked first), and no named alternative. The word "cutover" implies a migration end-phase, but nothing states the condition that should trigger this tool over mnemon_import_status or mnemon_import_database.

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