Skip to main content
Glama
nhype

OWA Exchange MCP Server

by nhype

empty_folder

Empty a mail folder by removing all items, with options to delete sub-folders and permanently delete items.

Instructions

Empty all items from a mail folder.

Args: folder_id: The Exchange folder ID to empty (from get_folders). delete_sub_folders: If True, also delete sub-folders. Default False. permanent: If True, permanently delete items (HardDelete). Otherwise move to Deleted Items. Default False.

Returns: JSON object with success status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folder_idYes
delete_sub_foldersNo
permanentNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

Covers delete_sub_folders and permanent deletion options, but omits important behaviors like permissions required, error handling, or what happens with the folder itself when delete_sub_folders is true. No annotations provided to supplement.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Concise with clear Args/Returns structure. Each sentence adds value, though 'Args:' section could be integrated more smoothly.

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?

Covers basic intent and parameters, but lacks behavioral details like permission requirements and edge cases. Output schema exists, so return value description is sufficient but minimal.

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

Parameters5/5

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

The description fully explains all three parameters including folder_id source and default behaviors for delete_sub_folders and permanent. With 0% schema coverage, this description compensates completely.

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?

Clearly states emptying all items from a mail folder. Identifies the action and resource, but does not explicitly distinguish from sibling delete_folder which removes the folder itself.

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 on when to use this tool versus alternatives like delete_folder. Does not mention prerequisites beyond folder_id, nor when not to use it.

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/nhype/owa-exchange-mcp'

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