Skip to main content
Glama
Sign In

Prubex

by com.prubex
OverviewDiscussionsAdmin

Move a message to a folder

mail_move
Idempotent

Moves a message to another folder of the same account and returns its id there (some providers change it). Use it to file mail; get the folder_id from mail_list_folders, and use mail_archive or mail_trash for those. A move into Trash counts as mail_trash, which the account policy can refuse. Example: { "message_id": "msg_…", "folder_id": "fld_…" }.

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": {
      "message_id": "<message_id>",
      "folder_id": "<folder_id>"
    },
    "name": "mail_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
folder_idYesA folder id (`fld_…`) from mail_list_folders.
message_idYesA message id (`msg_…`) from a list or search.

Output Schema

NameRequiredDescriptionDefault
message_idYesThe message's id after the move (it can change).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds useful behavioral context beyond those annotations: provider-dependent id changes after a move and account-policy refusal when moving to Trash. It does not elaborate on response shape, but an output schema exists.

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 front-loaded with the core action and return behavior, then gives usage routing, a policy caveat, and a brief example. Every sentence serves a purpose and there is no redundant filler.

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 two-parameter move tool with an output schema and rich annotations, the description covers the main action, folder source, alternatives, Trash semantics, policy refusal, and return-id caveat. Nothing essential for correct invocation is missing.

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 both parameters are already fully documented in the schema. The description reinforces the folder_id source and provides an example, but adds little semantic detail beyond what the schema already provides, so the baseline 3 applies.

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?

The description states a specific verb and resource: moving a message to another folder of the same account, and notes the return value. It also distinguishes this from mail_archive and mail_trash, so an agent can identify the correct tool without opening sibling schemas.

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?

It explicitly says to use this tool to file mail, tells where to obtain folder_id via mail_list_folders, and directs archive/trash cases to mail_archive or mail_trash. It further clarifies that moving into Trash counts as mail_trash and may be refused by account policy.

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

All Prubex toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources