onedrive_list_files

Browse and list Microsoft OneDrive files and folders using AI agents. Enables Claude, Cursor, and Windsurf to access cloud storage contents on your Mac.

Instructions

List files and folders in OneDrive

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Implementation Reference

server.js:82-86 (registration)
Registration of onedrive_list_files as a stub tool. All tools in the TOOLS array are registered here using server.tool() with an empty schema and a stub handler that returns an installation 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:51-51 (registration)
Definition of the onedrive_list_files tool in the TOOLS array with its description "List files and folders in OneDrive".
```
["onedrive_list_files", "List files and folders in OneDrive"],
```

Tool Definition Quality

B3/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to mention pagination behavior, whether deleted/shared items are included, what metadata is returned, or any permission requirements. The description only states the basic action without operational details.

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 extremely brief at seven words. While efficient and front-loaded with the key action, its brevity contributes to under-specification given the lack of annotations or output schema. No wasted words, but too minimal for the context.

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?

Given the absence of input parameters, output schema, and annotations, the description should compensate by explaining the return structure or scope limitations (e.g., root directory only, pagination). It provides neither, leaving the agent uncertain about what data structure will be returned or how to navigate large file sets.

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 input schema contains zero parameters. According to scoring rules, zero parameters establishes a baseline score of 4, as there are no parameter semantics to elaborate upon in the description.

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

Purpose4/5

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

The description clearly states the verb (List) and resource (files and folders in OneDrive), providing specific action and scope. However, it does not differentiate from the sibling tool 'onedrive_search_files' or clarify if this browses the root directory, a specific path, or operates recursively.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not clarify when to prefer this over 'onedrive_search_files' for browsing versus searching, nor when to use 'finder_list' for local files versus OneDrive cloud files.

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