Skip to main content
Glama
Sign In
mcp-outlook-applescript

mcp-outlook-applescript

by hasan-imam
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

prepare_move_email

Prepare an email for moving to another folder. Returns a preview, folder details, and an approval token for confirmation. Token expires in 5 minutes.

Instructions

Prepare to move an email to another folder. Returns a preview of the email, destination folder details, and an approval token. Call confirm_move_email with the token to execute the move. Returns an error if the email or destination folder ID does not exist. The token expires after 5 minutes.

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": {
      "email_id": "<email_id>",
      "destination_folder_id": "<destination_folder_id>"
    },
    "name": "prepare_move_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
email_idYesThe email ID to move (e.g., from list_emails or search_emails)
destination_folder_idYesThe destination folder ID (e.g., from list_folders)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries full burden. It discloses non-execution (requires confirm), return of preview and token, error on invalid IDs, and token expiry. Could explicitly state 'this does not move the email' but the flow implies it.

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?

Four focused sentences, front-loaded with the main purpose. Every sentence adds essential operational detail without fluff.

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

Completeness4/5

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

Covers purpose, return value, next step, error conditions, and token expiration. With no output schema or annotations, this is sufficiently complete for a two-parameter prepare operation.

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 description coverage is 100%, so baseline applies. The description adds existence-check context but no new parameter semantics beyond what the schema already provides.

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 the specific action 'Prepare to move an email to another folder', clearly distinguishing it from confirm_move_email and batch variants. The verb+resource is unambiguous.

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?

Explicitly instructs to call confirm_move_email with the token, establishing a clear two-step flow. Does not explicitly mention the batch alternative, but sibling names and the description's focus on single-email move make the context clear.

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