Skip to main content
Glama
io.github.shafty023/agent-maildir

io.github.shafty023/agent-maildir

mailbox_bind

Bind the current session to a registered mailbox agent ID so incoming messages are pushed here and unread messages are delivered immediately.

Instructions

Bind this session to a registered mailbox agent id so its messages are pushed here. Unread messages are delivered 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": {
      "agent": "<agent>"
    },
    "name": "mailbox_bind"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentYesRegistered agent id, e.g. claude-reviewer

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 behavioral burden. It does disclose two useful traits: delivery is push-based to this session and unread messages are flushed immediately. It omits whether binding replaces an existing binding, whether the call is idempotent, what error occurs for an unregistered id, and whether an unbind counterpart exists.

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?

Two short sentences with zero waste; the core action is front-loaded and the delivery consequence follows immediately. Nothing is repeated or padded.

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 session-binding tool with no output schema, the description covers the essential action and its immediate effect. The remaining gaps are edge-case behavior around rebinding and registration failures, which are secondary but would matter in practice.

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% and the single parameter is documented with an example, so the baseline applies. The description adds only the qualifier 'registered,' which reinforces that the id must already exist in the mailbox registry, but gives no syntax or validation detail beyond the schema.

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: bind the current session to a registered mailbox agent id, with the stated effect that messages are pushed to this session. That is clear enough to act on, but it never names or distinguishes itself from the closest sibling, mailbox_join, which an agent could easily mistake for the same operation.

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 agent should call this when it wants inbound messages pushed to the current session. There is no explicit when-to-use versus when-not, no mention of prerequisites (must the agent already be registered via mailbox_join?), and no guidance on what to do if a session is already bound.

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