Skip to main content
Glama
lanchuske

Pilot MCP

by lanchuske
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

onedrive_root

List all mounted OneDrive directories to locate your cloud files directly from your Mac.

Instructions

List mounted OneDrive directories

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.js:106-109 (registration)
    The tool 'onedrive_root' is registered in the TOOLS array and added to the MCP server via server.tool(). However, this is a stub — the real implementation is in a native binary.
    for (const [name, desc] of TOOLS) {
  server.tool(name, desc, {}, async () => ({
    content: [{ type: "text", text: "This is an inspection stub. Install Local MCP: npx -y local-mcp@latest setup" }],
  }));
  • server.js:57-57 (schema)
    Tool definition for 'onedrive_root' with description 'List mounted OneDrive directories'. This is just a stub definition.
    ["onedrive_root", "List mounted OneDrive directories"],

Tool Definition Quality

A3.5/5.0
Behavior2/5

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

No annotations exist, so the description carries full burden. It does not disclose output format (e.g., paths, names), whether hidden directories are included, or any side effects. The read-only nature is inferred but not stated.

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?

The description is a single sentence of 4 words, highly concise and front-loaded. Every word is meaningful with no redundancy.

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

Completeness3/5

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

The tool is simple with no parameters or output schema. The description adequately states the purpose, but omits expected return structure (e.g., list of directory names/paths), leaving some ambiguity for the agent.

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?

No parameters exist, and schema coverage is 100%. The description adds value by clarifying that it lists 'mounted' directories, which goes beyond the name 'onedrive_root'. Baseline for 0 parameters is 4.

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?

The description 'List mounted OneDrive directories' clearly states the action and resource, using a specific verb and noun. It distinguishes from sibling tools like 'onedrive_list_files' which lists files, not directories.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., onedrive_list_files for browsing subdirectories). The description lacks context on prerequisites or typical use cases.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lanchuske/local-mcp-releases'

If you have feedback or need assistance with the MCP directory API, please join our Discord server