Skip to main content
Glama
Sign In
m365-organizer

m365-organizer

by Denovarix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

drive_list

Lists OneDrive folder contents by path, using root when no path is given, to inspect files and subfolders.

Instructions

List OneDrive items at a folder path ('' = root).

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": "drive_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden; it does clearly imply a read-only listing and explains the root-path convention. However, it omits important behavioral details such as whether results are paginated, whether listing is recursive or immediate-children-only, and whether hidden or deleted items are included.

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 short sentence with zero wasted words, and the root-path hint is stated immediately after the core action. It is appropriately sized for a one-parameter tool.

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, the description needn't explain return values, and the one optional parameter is partially covered. Nevertheless, for a listing tool the description should say more about result shape or listing depth, which it leaves entirely unaddressed.

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 description coverage is 0%, so the description must compensate, and it does meaningfully: it explains that the path parameter denotes a folder path and that an empty string means the root. It stops short of describing path formatting, but it adds real meaning beyond the bare string schema.

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 uses a specific verb and resource ('List OneDrive items') and names the scope ('at a folder path'), so an agent can tell it apart from mutation siblings like drive_create_folder and drive_move. It is not quite a 5 because it doesn't explicitly contrast itself with any sibling or clarify whether the listing is flat or recursive.

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?

There is no guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. Usage is only implied by the verb 'List' and the path argument.

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

Deploy Server

Other Tools