Skip to main content
Glama
Sign In

Onedrive

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Onedrive List Files

onedrive_list_files
Read-onlyIdempotent

List files and folders in a OneDrive (Microsoft 365) folder. Pass a folder path relative to the drive root (e.g. "Documents" or "Documents/Reports"); omit to list the root. Returns each item's id, name, size, whether it is a folder, last-modified time, and web URL. Use to browse a user's OneDrive documents.

Input Schema

NameRequiredDescriptionDefault
topNoMaximum number of items to return (default 50, max 200).
pathNoFolder path relative to the OneDrive root, e.g. "Documents" or "Documents/Reports". Omit or leave empty for the root folder.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "path": "Documents"
+  },
+  {
+    "path": "Documents/Reports",
+    "top": 100
+  }
+]
  2. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, and idempotentHint=true. The description adds that the tool returns a list with specific fields (id, name, size, isFolder, last-modified time, web URL), which is useful but does not provide further behavioral context like authentication or rate limits. The description does not contradict annotations.

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 extremely concise: two sentences covering purpose, usage, return fields, and use case. No redundant or filler words. Every sentence contributes actionable information.

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

Completeness4/5

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

Given the tool has 2 parameters, no output schema, and annotations providing safety context, the description covers the core functionality, usage instructions, and return fields. It lacks mention of the 'top' parameter for pagination, but the schema covers that. Overall, it is mostly complete for a browsing tool with good schema and annotations.

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% with both parameters described. The description adds extra value by stating 'Pass a folder path relative to the drive root' and providing concrete examples ('Documents', 'Documents/Reports'), which aids understanding beyond the schema's formal descriptions. This clarifies the relative path semantics.

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 clearly states the tool lists files and folders in a OneDrive folder, specifying the verb and resource. It provides example paths and distinguishes from siblings like onedrive_get_file (which retrieves a specific file) and onedrive_search_files (which searches across folders). The purpose is specific and unambiguous.

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?

The description explains how to use it: pass a folder path relative to the root, or omit for root. It states 'Use to browse a user's OneDrive documents,' giving a clear usage context. However, it does not explicitly mention when not to use it or contrast with alternative sibling tools, though sibling names are available in the context.

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

All Onedrive toolsInspect
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.

Resources