Skip to main content
Glama

migration_plan

Read-onlyIdempotent

Prepares phased source-to-target migration plans with discovery, pilot, migration, and rollback gates, including AWS Transform integration discovery.

Instructions

Prepare phased discovery, pilot, migration and rollback gates; includes AWS Transform integration discovery.

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": {
      "source": "<source>",
      "target": "<target>",
      "strategy": "<strategy>"
    },
    "name": "migration_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYes
targetYes
strategyYes
constraintsNo

Output Schema

NameRequiredDescriptionDefault
kindNo
phasesNo
sourceNo
targetNo
sourcesNo
strategyNo
nextToolsNo
validatedNo
limitationNo
constraintsNo
integrationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • changedInput schema / required
      Previous value: -[
      -  "source",
      -  "target",
      -  "strategy",
      -  "constraints"
      -]New value: +[
      +  "source",
      +  "target",
      +  "strategy"
      +]
  2. First observedv0.4.1

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds genuine context about what the plan contains (phased gates including rollback) and that it pulls in AWS Transform integration discovery, which implies a read-only research step. It does not discuss determinism of output or depth of the generated plan.

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 with no filler; the verb and deliverable come first and the AWS Transform detail follows. Slight density of jargon ('gates', 'AWS Transform') without unpacking, but nothing is wasted.

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?

An output schema exists so return values need no explanation, and annotations cover safety. However, for a four-parameter planning tool with 0% schema coverage and a required strategy enum, the description leaves the caller guessing about input formats and about how this differs from adjacent planning tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description mentions no parameters at all. The critical ambiguity is 'source' and 'target' — free-text strings up to 4000 characters whose expected format (account ID, region, hostname, workload name) is documented nowhere. With zero coverage the description was required to compensate and does not.

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 names a specific artifact (a phased migration plan) and enumerates its contents: discovery, pilot, migration and rollback gates, plus AWS Transform discovery. That is clearly more than a restatement of the name. It stops short of distinguishing itself from close siblings such as implementation_plan or dr_strategy, which an agent must infer.

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 when-to-use guidance, no prerequisites, and no mention of alternatives. An agent cannot tell from the text whether this supersedes or complements implementation_plan, dr_strategy, or capacity_plan, all of which plausibly overlap with migration planning.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.