Skip to main content
Glama
Sign In
claude-mailbox

claude-mailbox

by zach-source
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

deregister

Leave the mailbox cleanly by releasing leadership, marking tasks done, and closing the active bead. Ensures proper cleanup when exiting a session.

Instructions

Cleanly leave the mailbox: release leadership, mark done, close bead.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "deregister"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description must disclose behaviors. It lists effects (release leadership, mark done, close bead) but does not mention prerequisites, reversibility, or consequences of misuse. Adequate but not thorough.

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?

Extremely concise: one sentence with a colon-separated list. No wasted words, front-loaded key actions.

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?

Given zero parameters and an output schema, the description is sufficient for a simple exit tool. It distinguishes from siblings adequately, though slightly cryptic phrasing reduces completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters exist, baseline score 4. The description adds meaning beyond schema by explaining the tool's purpose, though parameter details are not needed.

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 clearly states the goal 'Cleanly leave the mailbox' and lists three specific actions, distinguishing it from registration tools. However, 'close bead' is ambiguous and may confuse agents unfamiliar with domain terminology.

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?

No explicit guidance on when or when not to use the tool. Usage is implied (leave mailbox), and sibling tools like 'register_session' provide contrast, but no alternatives or conditions are mentioned.

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

Deploy Server

Other Tools