llm-migrate

Overview Schema Source Related Servers Discussions Admin

Generate Migration Report

generate_migration_report

Generate a human-readable migration report after analyzing a Python application and its source and target models, providing a reviewable plan with evidence gates before code changes.

Instructions

Generate a human-readable report from the integrated migration workflow.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`source`	Yes
`target`	Yes
`prompt_sources`	No
`source_endpoint`	No
`source_platform`	No
`target_endpoint`	No
`target_platform`	No
`application_path`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.3.0Sep 19, 2026

addedInput schema / properties / prompt_sources

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

Changed2 schema fields changedv1.2.0Sep 16, 2026

addedInput schema / properties / source_endpoint

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedInput schema / properties / target_endpoint

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

First observedv1.1.0Aug 31, 2026

TDQS

C2.4/5.0

Behavior2/5

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

With no annotations, the description must fully disclose side effects and operational traits. It says 'generate a human-readable report', which implies a read-like operation, but it never states whether this tool actually runs migrations or modifies anything. It also fails to mention any safety, auth, or side-effect details. The disclosure is minimal and incomplete.

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

Conciseness3/5

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

The description is a single concise sentence with no fluff or redundancy. However, it is under-specified and does not provide enough structural detail to be genuinely useful. It is appropriately sized in length but not in content, so it only partially earns its place.

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

Completeness1/5

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

Given a tool with 8 parameters (3 required) and no output schema visible, the description is drastically incomplete. It does not explain what the 'integrated migration workflow' entails, what inputs are needed, what the report contains, or any relationship to the migration process. An agent has virtually no context to call this tool correctly.

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?

The schema has 0% description coverage, and the description adds no meaning for any of the 8 parameters. It does not explain what source, target, application_path, or the optional fields represent, nor how they are used to generate the report. The burden falls entirely on the description, and it fails to compensate.

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 clearly states a verb (generate) and a resource (human-readable report), and it conveys the output type. However, it does not differentiate from sibling tools like generate_migration_plan or generate_session_migration_plan, which also produce migration-related outputs. It is clear but lacks distinction.

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?

The description provides no guidance on when to use this tool versus the many sibling migration tools. It does not mention any preferred scenario, exclusions, or alternatives. An agent receives no help in selecting between this and other plan/report tools.

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