OneDrive MCP Server

move_file

Move or rename files and folders in OneDrive by specifying source and destination paths, simplifying file organization and management.

Instructions

Mueve o renombra un archivo o carpeta.

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": {
      "sourcePath": "<sourcePath>",
      "destinationPath": "<destinationPath>"
    },
    "name": "move_file"
  }
}

Input Schema

Name	Required	Description	Default
`sourcePath`	Yes	Ruta origen con prefijo
`destinationPath`	Yes	Ruta destino con prefijo (incluye el nuevo nombre si renombras)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It only states the basic action (move/rename) without mentioning whether the operation is destructive, whether overwrites occur, or any permission requirements. For a mutation tool, this is insufficient.

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?

The description is a single sentence with no unnecessary words. It directly states the action and object, making it front-loaded and easy to parse.

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 has no annotations and no output schema, the description is too minimal. It does not explain what happens on success, whether the operation is reversible, or any edge cases. For a mutation tool, this leaves significant gaps in the agent's understanding.

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?

The schema descriptions for sourcePath and destinationPath already explain the parameter meanings (with prefixes and renaming behavior). Since schema coverage is 100%, the description adds little beyond what the schema provides, but it does confirm the action context.

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 the tool moves or renames a file or folder, which is a specific verb+resource combination. It distinguishes from siblings like copy_file and delete_file by the action, but does not explicitly mention alternatives or scope.

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 gives no guidance on when to use this tool versus alternatives. It does not mention scenarios where moving/renaming is preferred over copying or deleting, nor any 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