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

io.github.shafty023/agent-maildir

mailbox_status

Inspect which mailboxes the current agent session is bound to, including unread counts, orchestrator lease state, and active listeners, so you can verify routing and coordination before sending or waiting for messages.

Instructions

Show which mailbox agents this session is bound to, their unread counts, the orchestrator lease, and live listeners.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does reveal the return contents (per-agent unread counts, lease, listeners), which implies a non-mutating status read, but it never states that it is read-only, whether the lease/listener data is sensitive, or what underlying system state must exist for meaningful output. The enumerated payload is useful context, but safety and side-effect guarantees remain implicit.

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 front-loaded sentence enumerates the returned information with no filler, hedges, or repetition. Every clause adds a distinct returned field.

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?

With no output schema and no annotations, the description must convey what comes back, and it does list the four payload categories. It falls short of fully describing shape or meaning for terms like "orchestrator lease" and "live listeners," which an agent may not know how to interpret, but for a zero-parameter status tool this is close to sufficient.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. Nothing in the description misleads about inputs, and the implicit session-scoped behavior is consistent with an empty 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 uses a specific verb ("Show") and enumerates the exact resource set returned: session-bound mailbox agents, unread counts, the orchestrator lease, and live listeners. That makes the tool's function unambiguous, though it never explicitly contrasts itself with siblings like mailbox_inbox or mailbox_read, leaving disambiguation to the reader.

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 or when-not-to-use guidance and no named alternative. The phrase "this session is bound to" hints that it reports current binding state, but an agent gets no explicit rule for choosing this over mailbox_inbox or mailbox_read when it wants unread information.

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