Skip to main content
Glama

Freedom Agent Mail

delete_inbox

Delete an inbox and all of its email immediately.

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

Input Schema

NameRequiredDescriptionDefault
tokenYesThe inbox token returned by create_inbox.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the two most important behaviors: deletion is cascading ('all of its email') and immediate. It does not say whether the operation is permanent versus recoverable, whether the token is invalidated afterward, or what permission level is required — significant gaps for an irreversible mutation.

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?

One short sentence with the destructive scope and the immediacy constraint front-loaded; there is no filler whatsoever.

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 one-parameter, no-output-schema mutation tool the description explains what is removed and that it happens at once, which is close to adequate. The missing piece is recoverability and side effects on the token, which matter a great deal for an irreversible delete with no annotations to fall back on.

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?

The single required parameter is fully documented in the schema, including its origin ('returned by create_inbox'), so the baseline of 3 applies. The description adds no additional meaning about the token, such as whether it remains valid for other calls after deletion.

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?

The description gives a specific verb and resource ('Delete an inbox') plus the operation's scope ('and all of its email'), which makes it clearly distinguishable from the create/login/list/read/wait siblings. It stops short of the explicit sibling differentiation that a 5 would need, but the action is unambiguous.

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?

There is no when-to-use guidance, no preconditions (e.g. whether the caller must be logged in or own the inbox), and no mention of an alternative such as emptying messages without deleting the inbox. The agent is left to infer that this is the terminal cleanup tool from the word 'Delete' alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources