Local MCP

OneDrive Delete File

onedrive_delete_file

Destructive

Permanently deletes a file or an EMPTY folder inside the OneDrive folder synced on this Mac. It is not moved to the Mac's Trash, and OneDrive syncs the deletion to the cloud. Refuses a folder that still has items inside (it says how many) and any path outside a OneDrive folder. Called without confirm it returns a preview; pass confirm=true to delete. If OneDrive Files-On-Demand restores the item, the tool reports that the delete did not take instead of claiming success. Get the path from onedrive_list_files or onedrive_search_files.

Input Schema

Name	Required	Description
`path`	Yes	Absolute path to the file or folder
`confirm`	No	Must be true to delete
`remember`	No	With confirm: true, also stop asking for this kind of action from now on. Only when the person said so ("don't ask again"). The person can revoke it in LMCP or with set_always_allowed.

Output Schema

Name	Required	Description	Default
`path`	Yes
`deleted`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 24, 2026

addedInput schema / properties / remember

Added value: +{
+  "description": "With confirm: true, also stop asking for this kind of action from now on. Only when the person said so (\"don't ask again\"). The person can revoke it in LMCP or with set_always_allowed.",
+  "type": "boolean"
+}

First observedJun 30, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Goes well beyond the destructiveHint/readOnlyHint annotations: no Trash safety net, cloud sync propagation, dry-run preview without confirm, folder-count error message, and honest reporting when Files-On-Demand restores the item. These are exactly the failure modes an agent needs to know about.

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?

Front-loaded with irreversibility and scope, then refusals, then the confirm protocol, then the path source. Every sentence carries distinct operational information with no filler.

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

Completeness5/5

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

With an output schema present and annotations covering the safety profile, the description supplies all remaining decision-relevant context — irreversibility, refusal cases, preview semantics, and success-reporting caveats.

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?

Schema coverage is 100%, so the baseline is 3; the description adds real meaning to `confirm` by defining the preview-vs-delete split, though `remember` is left entirely to the schema.

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?

States a specific verb and resource ('Permanently deletes a file or an EMPTY folder') and scopes it precisely to 'inside the OneDrive folder synced on this Mac', which separates it from gdrive_delete_file and generic finder/file tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicit when-not conditions (refuses non-empty folders, refuses paths outside OneDrive), a prerequisite routing step ('Get the path from onedrive_list_files or onedrive_search_files'), and the confirm-gated workflow. An agent knows exactly when this applies and what to call first.

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

All Local MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.