Outlook Assistant

Overview Schema Source Related Servers Discussions Admin

move-emails

Move emails between Outlook folders by specifying email IDs and target folder. Organize your inbox by transferring messages to designated folders for better email management.

Instructions

Moves emails from one folder to another

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": {
      "emailIds": "<emailIds>",
      "targetFolder": "<targetFolder>"
    },
    "name": "move-emails"
  }
}

Input Schema

Name	Required	Description
`emailIds`	Yes	Comma-separated list of email IDs to move
`targetFolder`	Yes	Name of the folder to move emails to
`sourceFolder`	No	Optional name of the source folder (default is inbox)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Feb 13, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('moves') but doesn't cover critical aspects like whether this requires specific permissions, if the move is reversible, what happens to emails in the target folder, or potential rate limits. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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?

The description is a single, efficient sentence that directly states the tool's function without any unnecessary words. It is front-loaded with the core action and appropriately sized for its purpose, making it highly concise and well-structured.

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

Completeness2/5

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

Given the complexity of a mutation tool with no annotations and no output schema, the description is incomplete. It fails to address behavioral traits like error conditions, response format, or side effects, which are crucial for an AI agent to use this tool effectively. The minimal description leaves too many contextual gaps.

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?

The input schema has 100% description coverage, clearly documenting all three parameters. The description adds no additional semantic context beyond what the schema provides, such as explaining folder naming conventions or email ID formats. However, since the schema does the heavy lifting, the baseline score of 3 is appropriate.

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 clearly states the action ('moves emails') and the resources involved ('from one folder to another'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'list-emails' or 'search-emails' beyond the obvious action difference, which prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives like 'delete-event' or 'create-folder', nor does it mention prerequisites such as needing email IDs from 'list-emails' or 'search-emails'. It lacks explicit context about when this operation is appropriate, leaving usage decisions ambiguous.

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