Skip to main content
Glama
Sign In

BumbleBox

by ai.bumblebox
OverviewDiscussionsAdmin

Archive an email

archive_email
Idempotent

Moves one inbox email to its mailbox's archive folder, on the mail server too. Undone by restore_to_inbox. Nothing is deleted.

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>"
    },
    "name": "archive_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
email_idYesEmail id, as returned by search_emails or list_to_answer.

Output Schema

NameRequiredDescriptionDefault
movedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing that the move propagates to the mail server and that it is reversible via restore_to_inbox. 'Nothing is deleted' restates destructiveHint=false rather than adding new information, and no auth or rate-limit context is given.

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?

Three short sentences, each carrying distinct information: action and scope first, then the reversal path, then the non-destructive guarantee. No 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 one-parameter, idempotent, non-destructive mutation with an output schema, the description covers what an agent needs: destination, server-side effect, reversibility, and non-deletion. Nothing material 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?

With a single parameter at 100% schema coverage (including the source hint 'as returned by search_emails or list_to_answer'), the schema already does the work. The description only implies single-email granularity through 'one inbox email'.

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 and resource (moves one inbox email to its mailbox's archive folder) and adds the server-side scope. It implies the contrast with move_email/trash_email through 'archive folder' and 'nothing is deleted' but never names those siblings.

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?

'Nothing is deleted' implies when to prefer this over trash_email, and 'Undone by restore_to_inbox' names the reversal path. There is no explicit 'use when' clause or named alternative for the generic move case, so it stops just short of full routing guidance.

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

All BumbleBox 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