Skip to main content
Glama
Sign In
@forgespace/ui-mcp

@forgespace/ui-mcp

Official
by Forge-Space
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

forge_migrate

Generates a comprehensive migration plan for legacy projects including health assessment, strategy, strangler pattern, TypeScript migration, dependency analysis, and phased roadmap with quality gates.

Instructions

Generate a full migration plan for a legacy project. Combines health assessment with strategy recommendation, strangler boundaries, TypeScript migration plan, dependency risks, and a phased roadmap with quality gates.

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": {
      "directory": "<directory>"
    },
    "name": "forge_migrate"
  }
}

Input Schema

NameRequiredDescriptionDefault
directoryYesAbsolute path to the project directory
max_filesNoMaximum files to scan (default: 500)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.25.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations provided, so the description must fully disclose behavior. It states it generates a plan combining multiple assessments but does not clarify if the tool is read-only, what side effects exist, or required permissions. The absence of behavioral context is a significant gap.

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?

The description is a single sentence that front-loads the core purpose. While it is efficient and clear, it could benefit from slight restructuring for readability, but overall it is well-prioritized.

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?

Given the tool's complexity (generating a migration plan with multiple components), the description omits return format details and prerequisites. No output schema exists, so the description should explain what the agent can expect as output. This incompleteness limits the agent's ability to use the tool effectively.

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% and both parameters ('directory' and 'max_files') are self-explanatory from their schema descriptions. The tool description adds no additional semantic meaning beyond what the schema provides, meeting the baseline expectation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's verb ('Generate') and resource ('full migration plan'), and lists specific components (health assessment, strategy recommendation, etc.), distinguishing it from sibling tools like forge_assess and generate_migration_plan.

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?

No guidance on when to use this tool versus alternatives (e.g., forge_assess, generate_migration_plan). The description lacks context for selection, leaving the agent without direction on prerequisites or exclusions.

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