OneDrive MCP Server

create_folder

Create a folder in OneDrive, including any intermediate subfolders in the path. Specify the full folder path to establish your directory structure.

Instructions

Crea una carpeta (y subcarpetas intermedias si es necesario).

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": {
      "folderPath": "<folderPath>"
    },
    "name": "create_folder"
  }
}

Input Schema

Name	Required	Description	Default
`folderPath`	Yes	Ruta completa con prefijo de la carpeta a crear, ej: 'onedrive/PROYECTOS BIT/NuevaCarpeta'

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

A3.8/5.0

Behavior3/5

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

The description discloses a key behavior—creating intermediate subfolders if needed—which goes beyond the schema. However, it doesn't address idempotency, existing folder behavior, or permissions. With no annotations, the description carries the full burden and is only partially transparent.

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?

A single, clear sentence that is front-loaded with the action and includes the only essential nuance (recursive creation). No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (one fully documented parameter, no output schema), the description adequately covers the core operation and a key behavior. It doesn't discuss edge cases, but these are less critical for a straightforward creation tool.

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 provides a complete description of the folderPath parameter with an example, so the description adds no additional parameter semantics. Baseline 3 is appropriate for high 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?

The description clearly states the action ('Crea una carpeta') and the resource (folder), and adds a distinguishing behavioral detail (creates intermediate subfolders). This distinguishes it from sibling file operations like write_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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not explicitly state when to use this tool versus alternatives. While it is the only folder-creation tool, there is no guidance on prerequisites, error conditions, or comparisons to similar operations.

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

Deploy Server