Skip to main content
Glama
Sign In
himalaya-mcp

himalaya-mcp

by Data-Wise
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

move_email

Move an email to a specified folder such as Archive, Trash, Spam, Sent, or Drafts to organize your mailbox.

Instructions

Move an email to a different folder. Common targets: Archive, Trash, Spam, Sent, Drafts.

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": {
      "id": "<id>",
      "target_folder": "<target_folder>"
    },
    "name": "move_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesEmail message ID
folderNoSource folder name (default: INBOX)
accountNoAccount name (uses default if omitted)
target_folderYesDestination folder name (e.g. 'Archive', 'Trash')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.2.2
    • addedInput schema / properties / id / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "maximum": 9007199254740991,
+    "minimum": 0,
+    "type": "integer"
+  }
+]
    • removedInput schema / properties / id / type
      Removed value: -"string"
  2. First observedv1.7.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and largely drops it. It does not say whether a move is reversible, whether moving to Trash/Spam is effectively destructive, what happens if target_folder does not exist, or whether the source folder matters. The only added context is the enumeration of typical target folders.

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?

Two short sentences, operation first and destination examples second; no filler or restated boilerplate. Every phrase contributes information an agent can act on.

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 4-parameter mutation tool with zero annotations and no output schema, the description covers the core action and common targets but omits failure modes, reversibility, and side effects on the source folder. It is enough to attempt a correct call, but not enough to predict consequences.

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 all four parameters are documented in the schema itself, setting the baseline at 3. The description lightly extends target_folder semantics with a concrete target list, but adds nothing about id format, the source `folder` default, or the `account` scoping.

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?

"Move an email to a different folder" states a specific verb and resource with the destination concept named, so an agent immediately knows the operation. It does not differentiate from any sibling (e.g. snooze_email, which also relocates a message), but no sibling is a direct move-tool duplicate, so confusion risk is limited.

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 never states when to use this versus alternatives such as snooze_email or delete_folder, nor any prerequisites (e.g. target folder must exist). The "Common targets" list hints at valid destinations but is not when-to-use guidance.

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