Skip to main content
Glama
Sign In

BumbleBox

by ai.bumblebox
OverviewDiscussionsAdmin

Put an email in the trash

trash_email
Idempotent

Moves one inbox email to its mailbox's trash when BumbleBox certifies it as noise (spam, newsletter, promotion, with a unanimous safety vote and no known contact or action word). Any other email is not moved: it becomes a proposal the user confirms in one tap in BumbleBox. Never a permanent deletion; undone by restore_to_inbox.

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": "trash_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoWhy, shown to the user with a proposal.
email_idYesEmail id, as returned by search_emails or list_to_answer.

Output Schema

NameRequiredDescriptionDefault
resultYes

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?

Adds real behavioral detail beyond the annotations: the certification gate, the proposal fallback the user confirms, and the restore path. 'Never a permanent deletion' overlaps destructiveHint=false, but the conditional-eligibility behavior is information no annotation carries. Missing only operational details such as auth or rate limits.

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 sentences, front-loaded with the action and its gate, then the fallback, then reversibility. The parenthetical condition list is dense but every clause carries decision-relevant meaning; nothing is redundant.

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?

With an output schema present, return values need no explanation. The description covers eligibility, fallback, and reversibility for a two-parameter mutation tool, leaving no gap an agent would need filled before calling it.

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 email_id and reason are already documented at the field level, setting the baseline at 3. The description never mentions the reason parameter, which is user-visible in proposals, so it adds nothing beyond the schema.

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 and resource ('Moves one inbox email to its mailbox's trash') plus the precise gating condition. It clearly separates itself from siblings like move_email and archive_email by scoping to the certification-based noise path and naming restore_to_inbox as the inverse.

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?

Explicitly defines when the tool acts (spam, newsletter, promotion, unanimous safety vote, no known contact or action word) and what happens when it does not ('any other email is not moved: it becomes a proposal the user confirms in one tap'). That is an explicit when/when-not rule with the alternative behavior spelled out.

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