Skip to main content
Glama
m365-organizer

m365-organizer

by Denovarix

mail_move_from_senders

Bulk-move existing emails from specified senders or @domain entries into a destination folder, creating it if missing. Use it to organize Outlook mail by sender in one step.

Instructions

Bulk-move existing mail from addresses or '@domain' entries into dest_path (created if missing).

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": {
      "senders": "<senders>",
      "dest_path": "<dest_path>"
    },
    "name": "mail_move_from_senders"
  }
}

Input Schema

NameRequiredDescriptionDefault
folderNoinbox
sendersYes
dest_pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations are absent, so the description carries the full burden. It does disclose two useful behaviors: the operation is bulk, and dest_path is created if missing. It says nothing about whether the move is reversible, what happens to mail already in the destination, whether subfolders are traversed, or any permissions/rate constraints on a write operation.

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?

A single front-loaded sentence with zero filler. It is efficient, though the brevity borders on under-specification rather than optimal concision.

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?

For a destructive-ish bulk write with no annotations and no schema descriptions, the definition leaves key facts unstated: the source folder parameter, reversibility, and what the response contains (an output schema exists, so returns need not be explained). As written, an agent could call this without knowing it defaults to scanning only the inbox.

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

Parameters2/5

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

Schema description coverage is 0% across 3 parameters, so the description must compensate and only partly does. It clarifies senders (plain addresses or '@domain' entries) and dest_path (auto-created), but the 'folder' parameter — which controls the source folder, defaulting to inbox — is never mentioned anywhere.

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?

States a specific verb+resource ('Bulk-move ... mail') plus the source ('addresses or @domain entries') and destination, which is enough to distinguish it from drive_move and the rule-management siblings. It does not say which mailbox folder is the source scope, leaving the operation slightly underspecified.

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 indication of when to use this versus mail_add_sender_rule or mail_list_rules, no prerequisites, and no exclusions. The agent has to infer usage entirely from the name and one line.

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