OneDrive MCP Server

copy_file

Copies a file or folder to a different location in OneDrive.

Instructions

Copia un archivo o carpeta a otra ubicacion.

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": "copy_file"
  }
}

Input Schema

Name	Required	Description	Default
`sourcePath`	Yes	Ruta origen con prefijo
`destinationPath`	Yes	Ruta destino con prefijo

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 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 carries the full burden for behavioral disclosure. It only states the basic copy action, omitting crucial details like overwrite behavior, recursive copying for folders, or potential errors.

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, efficient sentence with no fluff. It is appropriately front-loaded, though extremely terse.

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?

The tool has no annotations or output schema, and the description does not clarify important behaviors such as whether folders are copied recursively or if existing destination files are overwritten. The 'prefijo' parameter descriptions are also unexplained, leaving gaps for the agent.

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 description coverage is 100%, so the parameters already have descriptions. The tool description adds no extra meaning beyond the schema's 'Ruta origen con prefijo' and 'Ruta destino con prefijo', which remain somewhat ambiguous.

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 copies a file or folder to another location. The verb 'Copia' (copies) + resource 'archivo o carpeta' (file or folder) is specific and distinguishes it from siblings like move_file or 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 is provided on when to use this tool vs alternatives, no prerequisites, and no exclusions. The description only states what it does, not when to apply it.

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

Deploy Server