Local MCP

OneDrive Root

onedrive_root

Read-only

Lists all mounted OneDrive directories on this Mac. Start here for OneDrive — the mount paths it returns are what the other onedrive_* tools (onedrive_list_files, onedrive_read_file, onedrive_search_files) need. Each entry's permissions carries only the permissions this service has (read, send, write; a key that is missing does not apply). true: allowed in the account's boxes (LMCP's icon → My apps → open the app's row → the account's Read · Send · Write) and the item accepts it. false: turned off there, or the item is read-only (read_only: true).

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`roots`	No
`reason`	No	Only when roots is empty: cloudstorage_unreadable, no_cloud_folders or only_other_providers.
`message`	No	Only when roots is empty: why, and what to do.
`other_providers`	No	Only when roots is empty: the cloud providers that do have a folder on this Mac.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 22, 2026

addedOutput schema / properties / roots / items / properties / permissions

Added value: +{
+  "properties": {
+    "read": {
+      "type": "boolean"
+    },
+    "send": {
+      "type": "boolean"
+    },
+    "write": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / roots / items / properties / read_only

Added value: +{
+  "description": "true: the system reports this item as not modifiable. Absent when it cannot tell.",
+  "type": "boolean"
+}

Changed3 schema fields changedOct 10, 2026

addedOutput schema / properties / message

Added value: +{
+  "description": "Only when roots is empty: why, and what to do.",
+  "type": "string"
+}

addedOutput schema / properties / other_providers

Added value: +{
+  "description": "Only when roots is empty: the cloud providers that do have a folder on this Mac.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / reason

Added value: +{
+  "description": "Only when roots is empty: cloudstorage_unreadable, no_cloud_folders or only_other_providers.",
+  "type": "string"
+}

First observedJun 30, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/destructiveHint=false, so the description focuses its effort elsewhere: it discloses the shape of the `permissions` map, that a missing key means 'does not apply', the false conditions (turned off in the account's app row, or read_only: true), and where in the UI permissions are granted. That is substantive context beyond the annotations, though the return values are partly duplicated by the output schema.

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 purpose and the 'start here' routing are front-loaded in the first two sentences, and the remaining text is dedicated to permission semantics that would be hard to infer. The permissions sentence is dense and slightly overlong, but every clause carries information.

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 handling the return shape and annotations covering the safety profile, the description still supplies the one thing neither provides: that this is the required first call whose mount paths feed the other onedrive_* tools, plus how to read the permissions map. Nothing an agent needs in order to call it correctly is missing.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate; baseline 4 applies. No parameter text is wasted or missing.

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 ('Lists all mounted OneDrive directories on this Mac') and immediately distinguishes itself from the onedrive_* siblings by explaining that its mount paths are their prerequisite. An agent can tell it is the entry point rather than a file operation.

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

Usage Guidelines4/5

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

'Start here for OneDrive' plus the named dependencies (onedrive_list_files, onedrive_read_file, onedrive_search_files) gives a clear when-to-use signal. It lacks any explicit exclusion or contrast with analogous roots like gdrive_root or file_list, but for a zero-parameter discovery tool the guidance is strong.

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.