Skip to main content
Glama
dockndevai

@dockndevai/mcp-outlook

by dockndevai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List OneDrive items

list_drive_items
Read-onlyIdempotent

List files and folders in a OneDrive folder by path or item ID. Retrieve metadata like name, size, and last modified.

Instructions

List the files and folders in a OneDrive folder. Give a path relative to the drive root (e.g. "/Documents"), or an item_id from a previous result. Omit both for the root. Returns id, name, isFolder, size, childCount, lastModified, webUrl.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoFolder path from the drive root, e.g. "/Documents/Reports". Omit for root.
item_idNoFolder item id (from a previous list). Alternative to path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. Description adds return fields and clarifies that path and item_id come from previous results, which is useful context beyond annotations. No contradiction.

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?

Three sentences, all valuable. Example path given. No fluff or repetition.

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

Completeness5/5

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

Complete for a simple read tool. Provides all necessary info: how to target folder, what to expect in return.

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 covers both parameters fully. Description adds the relationship between path and item_id (alternatives) and that omitting both means root, which goes beyond schema descriptions.

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?

States a specific verb 'List' and resource 'files and folders in a OneDrive folder'. Clearly distinguishes from siblings like search_drive_files and get_drive_item by focusing on listing folder contents.

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?

Gives clear instructions on how to specify the folder: via path, item_id, or omit for root. Implies usage for navigation but does not explicitly name alternatives or exclusions; however, the context is sufficient for an agent to decide.

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