Skip to main content
Glama
Sign In

MailGlass

by email.dygc.mail
OverviewDiscussionsAdmin

delete_inbox

Soft-delete an inbox: it stops receiving mail and its address enters a 7-day reuse cooldown before it can be recreated.

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": {
      "inboxId": "<inboxId>"
    },
    "name": "delete_inbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
inboxIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose real behavioral traits: the delete is soft, mail delivery stops, and the address is locked for a 7-day reuse cooldown. It omits whether the inbox or its existing messages can be restored, what happens if the inboxId is unknown or already deleted, and any permission requirements.

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?

A single sentence with the operation and its consequences front-loaded; every clause (soft-delete, delivery stop, cooldown) adds distinct information. No filler or restatement of the tool name.

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

Completeness4/5

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

For a one-parameter tool with no output schema, the description gives enough to call it correctly and understand the primary side effect. The remaining gap is lifecycle detail — whether the inbox or its messages are recoverable and what an unknown ID returns — which matters for a destructive-sounding operation.

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?

One required parameter with 0% schema description coverage, so the description should compensate but does not mention inboxId at all. The parameter's meaning (the inbox to soft-delete) is inferable from context, so it is adequate rather than opaque.

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 ('Soft-delete an inbox') and immediately qualifies what soft-delete means, which is more than the name alone conveys. The resource scoping (inbox vs. message) separates it from delete_message without ambiguity.

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

Usage Guidelines3/5

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

Usage is only implied: the effect described (stops receiving mail, address cooldown) tells an agent why it might call this, but there is no explicit when-to-use or when-not guidance, and no sibling is named as an alternative. Nothing is misleading, but routing must be inferred.

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

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