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

io.github.shafty023/agent-maildir

mailbox_inbox

Lists unread, unacknowledged messages for a bound agent so it can check pending coordination updates before processing or acknowledging them.

Instructions

List unread (unacknowledged) messages for a bound agent.

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_inbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden; it does disclose that the operation is a non-destructive listing scoped to unread/unacknowledged messages for a bound agent. It says nothing about ordering, result limits, pagination, or whether it ever mutates read state, which are the traits an agent most needs for a polling tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no wasted words; the filtering qualifier and scope are packed into one clause. Its brevity is close to under-specification rather than verbosity, but structurally it is clean.

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 simple one-optional-parameter read tool with no output schema, the definition covers the essentials but leaves the agent's default behavior and any result-size limits unstated. Adequate, with clear gaps for an agent that must decide whether to pass 'agent' at all.

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 parameter at 0% schema coverage, so the description should compensate. The phrase 'for a bound agent' hints that the agent parameter selects the bound mailbox, but it does not say whether the parameter is optional, what happens when it is omitted (default to the caller's own binding?), or what an invalid/unbound value yields.

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?

States a specific verb plus resource ('List unread (unacknowledged) messages') and a scope ('for a bound agent'), which separates it from mailbox_read and mailbox_ack by filtering to unacknowledged mail. It stops short of naming an alternative explicitly, so it is clear but not fully differentiated.

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?

'for a bound agent' implies the precondition that the caller must be bound (cf. mailbox_bind), and 'unread (unacknowledged)' implies this is a triage/check step before mailbox_ack or mailbox_read. No explicit when-to-use versus when-not statement or named alternative is given.

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