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

io.github.shafty023/agent-maildir

mailbox_ack

Archive a handled message and notify its sender that it was processed, rejected, or deferred. Call it after the requested action is complete to close the coordination loop.

Instructions

Archive a handled message and send its sender an acknowledgement. Call only after the requested action is done, rejected, or deferred.

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": {
      "message_id": "<message_id>"
    },
    "name": "mailbox_ack"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
agentNo
statusNo
message_idYes

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?

With no annotations, the description must carry the safety profile itself. It does disclose the most important trait — an outward-facing side effect, sending the sender an acknowledgement — plus the mutation of archiving. However, it says nothing about reversibility of the archive, required permissions, or what happens on a repeated call, so the disclosure is only partial.

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 sentences, no filler, with the action stated first and the invocation condition second. Nothing could be removed without losing information.

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?

There are no annotations and no output schema, and the tool mutates state and contacts a third party, so the description should do more. It covers purpose and timing adequately but leaves parameter roles (note, agent) and any return/error expectations unexplained.

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

Parameters2/5

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

Schema description coverage is 0%, so the description needs to explain the four parameters and largely does not. The one contribution is mapping 'done, rejected, or deferred' onto the status enum values processed/deferred/rejected; note, agent, and message_id get no meaning at all beyond their names.

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 names two concrete actions on a specific resource: archive the message and send the sender an acknowledgement. That clearly separates it from read/list siblings such as mailbox_read or mailbox_inbox, though it never explicitly references a sibling to reinforce the distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a real precondition: only call once the requested action is done, rejected, or deferred. That is a usable timing rule whose three states line up with the status enum, but no alternative tool or fallback path is suggested if the action is still pending.

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