Skip to main content
Glama
Sign In
outlook-mcp

outlook-mcp

by jagarlamudisrinath
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

move_email

Move an email to a specified folder in Outlook using its entry ID and folder path.

Instructions

Move an email to another folder.

Args: entry_id: EntryID of the email to move. target_folder: Destination folder name or path.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "entry_id": "<entry_id>",
      "target_folder": "<target_folder>"
    },
    "name": "move_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
entry_idYes
target_folderYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations provided; description does not disclose side effects (e.g., whether the email is removed from the source folder, permissions needed, or if the operation is reversible). For a mutation tool, more behavioral context is needed.

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?

Extremely concise with a front-loaded verb-noun phrase followed by parameter descriptions. No extraneous text.

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?

For a simple move operation with an output schema present, the description is adequate but lacks details on error handling, what happens if the target folder doesn't exist, or confirmation of success.

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%; description provides basic meaning for both parameters ('EntryID of the email' and 'destination folder name or path'), adding value beyond the schema's type/title, but no format or constraints.

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 'Move an email to another folder' – a specific verb and resource. This distinguishes it from siblings like delete_email (delete) and forward_email (forward).

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 or any prerequisites. The description is purely declarative without usage context.

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