Skip to main content
Glama

onedrive_list

Read-only

Lists files and folders in a specified OneDrive path, such as / or /Documents/Taxes, so you can browse cloud storage contents.

Instructions

List a OneDrive folder by path, e.g. / or /Documents/Taxes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "onedrive_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo/

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that the operation is scoped to a single folder path, but says nothing about depth (one level vs recursive), pagination, or result limits — context that matters for a listing tool.

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?

A single front-loaded sentence with no filler; every clause (verb, resource, path format) contributes information the agent needs.

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?

Because an output schema exists, return values need not be explained. However, for a listing tool the description omits how deep the listing goes and whether results are paginated or capped, leaving a meaningful gap for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% for the single path parameter, so the description must compensate. It does give concrete path syntax examples ('/' and '/Documents/Taxes') and implies '/' is the root default, but does not explain relative vs absolute paths or trailing-slash behavior.

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?

States a specific verb and resource: 'List a OneDrive folder by path'. An agent can tell this is a directory-listing operation rather than a file read, though it never names or distinguishes itself from siblings like onedrive_search or onedrive_shared.

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

Usage Guidelines3/5

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

Usage is only implied — the listing verb plus path examples suggest 'use this to enumerate a folder's contents'. There is no guidance on when to prefer it over onedrive_search or onedrive_read, and no mention of prerequisites such as which drive/account is targeted.

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