Coding Agent MCP Server

by Sukarth

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

move_file

Moves or renames a file from source to destination. Optionally overwrites the destination file if it exists.

Instructions

Move/rename a file

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

Input Schema

Name	Required	Description
`source`	Yes	Source file path
`destination`	Yes	Destination file path
`overwrite`	No	Overwrite destination if it exists

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1May 29, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description should fully disclose behavior. It only states the basic action, omitting details like what happens if overwrite is false and destination exists, or permissions needed.

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, clear sentence with no waste. However, it could include more context while remaining concise, hence not a perfect 5.

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 tool with 3 parameters and no output schema, the description is too minimal. It fails to explain behavior on conflict, side effects, or how it differs from copying, making it incomplete.

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 all three parameters described in the input schema. The description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

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 'Move/rename a file' clearly states the verb (move/rename) and resource (file), distinguishing it from siblings like copy_file and delete_file.

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 vs alternatives like copy_file or overwrite scenarios; no prerequisites or context provided.

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