ts-refactor-mcp

Overview Schema Source Related Servers Discussions Admin

moveFile

Move a TypeScript file and automatically update all imports across the project. Atomic edits ensure consistent refactoring without breaking dependencies.

Instructions

Move a TypeScript file and update all imports automatically. Applies edits atomically.

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": {
      "projectRoot": "<projectRoot>",
      "oldPath": "<oldPath>",
      "newPath": "<newPath>"
    },
    "name": "moveFile"
  }
}

Input Schema

Name	Required	Description
`projectRoot`	Yes	Absolute path to the project root (where tsconfig.json is)
`oldPath`	Yes	Absolute path to the file to move
`newPath`	Yes	Absolute path to the new location
`dryRun`	No	If true, return the edit plan without applying changes

Schema Changelog

Changes observed during successful MCP inspections.

First observedJan 29, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Discloses key behavior: automatic import updates and atomic application. However, with no annotations, it lacks details on potential side effects (e.g., whether destination is overwritten, error handling for non-existent files).

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?

Two sentences, no fluff. Front-loaded with purpose, then key behavior. Every word earns its place.

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?

Adequate for a simple move tool, but lacks details on error conditions, overwrite behavior, and return value (no output schema). Could be more complete for reliable agent invocation.

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 covers all 4 parameters with descriptions. The description adds no extra semantics beyond restating the tool's purpose; baseline 3 is appropriate given full schema coverage.

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?

Description clearly states it moves a TypeScript file and automatically updates imports. The verb 'move' and resource 'TypeScript file' are specific, and the sibling tool 'warmup' is unrelated, so no confusion.

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?

No explicit guidance on when to use this tool versus alternatives. It implies it's for TypeScript files in a project, but does not mention prerequisites, caveats, or exclusion criteria.

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

moveFileA
warmupB