Skip to main content
Glama
adecubed

gigamail

by adecubed
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

move_message

Destructive

Move a message to another folder within one account. The first call returns a preview and needs out-of-band human approval before it executes.

Instructions

Move a message to another folder of the same account. TWO-PHASE, HUMAN-APPROVED: the first call (no request_id) executes nothing — it returns status=approval_required with a preview of exactly what would happen and a request_id. A human approves out of band (GigaMail console, CLI or Telegram, behind Windows Hello / Touch ID); the second call with that request_id executes the payload that was approved (the approved arguments, not the ones passed the second time). Requests expire (default 15 min); identical pending requests are deduplicated; more than 20 requests/hour per tool are refused (status=rate_limited). Every phase is written to the audit log. The preview shows the message's sender and subject and, above all, the folder it leaves and the folder it lands in, by readable name. Returns {success}. Nothing is destroyed and the move can be undone by moving the message back, but a move is enough to hide mail from the human who is supervising, so it is approved like any other action that changes what the mailbox looks like. Note: on IMAP the message gets a new UID in the destination folder, so the old message_id stops being valid. To delete a message use delete_message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folder_idYesDestination folder: id (Graph) or name (IMAP) from list_folders.
account_idNoAccount to operate on (integer id from list_accounts). Omit or null = the user's active account.
message_idYesMessage id exactly as returned by list_messages / list_unread / search_mail (opaque Graph id for Microsoft accounts, numeric IMAP UID for IMAP accounts). Ids are account-specific: never reuse one across accounts.
request_idNoOmit on the first call. On the first call the tool does NOT execute: it returns status=approval_required, a preview and a request_id. A human must approve that request_id out of band (GigaMail console, `gigamail approvals approve`, or Telegram — all behind Windows Hello / Touch ID). Then call again with the same request_id to execute. The agent cannot approve; repeating the call without approval just returns awaiting_approval.
source_folderNoFolder the message is currently in (IMAP only; empty = inbox).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.3
    • addedInput schema / properties / request_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Omit on the first call. On the first call the tool does NOT execute: it returns status=approval_required, a preview and a request_id. A human must approve that request_id out of band (GigaMail console, `gigamail approvals approve`, or Telegram — all behind Windows Hello / Touch ID). Then call again with the same request_id to execute. The agent cannot approve; repeating the call without approval just returns awaiting_approval.",
+  "title": "Request Id"
+}
  2. Changed4 schema fields changedv0.3.0
    • addedInput schema / properties / account_id / description
      Added value: +"Account to operate on (integer id from list_accounts). Omit or null = the user's active account."
    • addedInput schema / properties / folder_id / description
      Added value: +"Destination folder: id (Graph) or name (IMAP) from list_folders."
    • addedInput schema / properties / message_id / description
      Added value: +"Message id exactly as returned by list_messages / list_unread / search_mail (opaque Graph id for Microsoft accounts, numeric IMAP UID for IMAP accounts). Ids are account-specific: never reuse one across accounts."
    • addedInput schema / properties / source_folder / description
      Added value: +"Folder the message is currently in (IMAP only; empty = inbox)."
  3. First observedv0.1.3

TDQS

A4.4/5.0
Behavior4/5

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

Rich disclosure beyond annotations — two-phase approval, expiry, deduplication, rate limits, audit logging, and the IMAP UID-reassignment caveat that invalidates the old message_id. Would be 5 if it stated whether the out-of-band approval needs to happen within the same session or what happens if the payload arguments differ from the second call (partially covered by 'the approved arguments, not the ones passed the second time').

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?

Front-loads the verb+resource, then the critical two-phase constraint, then edge cases. Long but each sentence carries load. Could lose a clause or two (e.g. the Telegram/CLI enumeration) without much loss.

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

Completeness5/5

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

For a destructive, open-world, non-idempotent mutation with no output schema, the description covers approval mechanics, expiry, rate limits, audit trail, reversibility, and the IMAP UID side effect — everything an agent needs to call it correctly across two phases.

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 100%, so the schema already documents all five parameters, including request_id's two-call semantics. The description reinforces the request_id flow but adds no syntax or format detail beyond the schema. Baseline 3 is appropriate.

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 a specific verb (move) and resource (message) plus the scope constraint (another folder of the same account). The closing note distinguishes it from the sibling delete_message, and the preview description clarifies scope further.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit routing: use delete_message to delete; the two-phase approval flow is laid out step by step, including when to pass request_id and when not to. No inference required.

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