onedrive_delete_file

Delete files from Microsoft OneDrive using AI commands. Remove documents, photos, or folders from your cloud storage directly through Pilot MCP on macOS.

Instructions

Delete file from OneDrive

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Implementation Reference

server.js:82-86 (registration)

Registration of onedrive_delete_file tool along with all other tools in a loop. Each tool is registered with an empty schema and a stub handler that returns an inspection message.

for (const [name, desc] of TOOLS) {
  server.tool(name, desc, {}, async () => ({
    content: [{ type: "text", text: "This is an inspection stub. Install Pilot MCP on macOS: npx -y local-mcp@latest setup" }],
  }));
}

server.js:55-55 (registration)
Tool name and description entry for onedrive_delete_file in the TOOLS array
```
["onedrive_delete_file", "Delete file from OneDrive"],
```

Tool Definition Quality

C2.6/5.0

Behavior2/5

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

No annotations provided, so description carries full burden. While 'Delete' implies destruction, it fails to disclose whether deletion is permanent or reversible, required permissions, error handling, or explain the unusual absence of input parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely brief (4 words) with no redundancy, but severely under-specified for a destructive operation. The brevity reflects missing critical information rather than efficient communication.

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

Completeness1/5

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

Completely inadequate for a destructive operation with no annotations, no output schema, and an anomalous empty input schema. A delete tool requires explicit safety warnings, permanence disclosures, and parameter documentation, none of which are present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has zero parameters, establishing a baseline of 4 per scoring rules. However, the description misses the opportunity to explain how the target file is identified without parameters (e.g., via context or conversation state).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the basic action (delete) and target (OneDrive file) but fails to clarify how the target file is specified given the empty parameter schema. Does not distinguish from sibling onedrive_move_file or explain the deletion 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?

Provides no guidance on when to use versus alternatives (like onedrive_move_file for 'deleting' by moving to trash), no prerequisites, and no warnings about the destructive nature of the operation.

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

Install Server

Pilot MCP