onedrive_read_file

Read files from Microsoft OneDrive to analyze document contents, extract data, and integrate cloud storage into AI workflows without switching applications.

Instructions

Read file content from OneDrive

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Implementation Reference

server.js:82-86 (registration)
Tool registration loop that registers 'onedrive_read_file' with a stub handler. All tools in the TOOLS array are registered here with empty schema and a stub implementation 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:51-52 (registration)
Definition of 'onedrive_read_file' in the TOOLS array with its description 'Read file content from OneDrive'. This is where the tool name and description are defined before being registered.
```
["onedrive_list_files", "List files and folders in OneDrive"],
["onedrive_read_file", "Read file content from OneDrive"],
```

Tool Definition Quality

C2.5/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but fails significantly. It doesn't specify return format (string, bytes, or object), encoding handling, size limits, error behavior for missing files, or how the target file is identified given the empty parameter schema.

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?

The description is extremely concise (5 words) and front-loaded, but in this context, brevity becomes a liability. Given the empty parameter schema and lack of annotations, the description is inadequately sized to explain the tool's operation or the parameter anomaly.

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?

Despite being a simple read operation, the tool has no output schema, no annotations, and critically, no input parameters for file identification. The description fails to explain how the file target is specified, making it contextually incomplete for an agent attempting to invoke the tool.

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, which per the scoring guidelines establishes a baseline of 4. The description has no parameter information to add, but given the unusual nature of a file-reading tool having no file path parameter, additional context would have been valuable.

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?

The description states a clear verb ('Read') and resource ('file content from OneDrive'), but fails to distinguish from sibling tools like 'onedrive_list_files' or 'onedrive_search_files'. More critically, it doesn't address the absence of file identification parameters in the schema, leaving the agent confused about how to specify which file to read.

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

Usage Guidelines1/5

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

Provides no guidance on when to use this tool versus alternatives (e.g., 'onedrive_list_files' for browsing vs reading), nor does it mention prerequisites or required context like file paths. The complete absence of parameters makes this omission particularly severe.

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