Skip to main content
Glama

imap_mailbox_status

Read-onlyIdempotent

Retrieve total, unseen, and recent message counts for a specified mailbox without selecting it, so you can check status before opening or modifying the mailbox.

Instructions

Get mailbox message counts (total, unseen, recent) without selecting it

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": {
      "mailbox": "<mailbox>"
    },
    "name": "imap_mailbox_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
mailboxYesMailbox name to check status of
account_idNoAccount identifier (defaults to `"default"`)default

Output Schema

NameRequiredDescriptionDefault
dataYesTool-specific data payload
metaYesExecution metadata (timestamp, duration)
summaryYesHuman-readable summary of the operation outcome

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.12

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the bar is lower. The phrase 'without selecting it' still adds real value beyond them: it tells the agent that IMAP session state is untouched, which readOnlyHint alone does not unambiguously convey. It does not describe failure behavior for a nonexistent mailbox.

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 twelve-word sentence with the payload contents parenthesized and the key behavioral caveat front-loaded at the end. Nothing is redundant and nothing needs trimming.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a simple two-parameter read tool with full schema coverage, annotations covering the safety profile, and an output schema that carries return values. Purpose plus the no-selection caveat is everything an agent needs to call it correctly.

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 description coverage is 100%, with both 'mailbox' and 'account_id' documented in the schema itself, including the default value. The description adds no format hints (e.g., hierarchy delimiter, case sensitivity) or examples of mailbox names beyond what the schema already states, so the baseline of 3 applies.

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 a specific verb and resource ('Get mailbox message counts') and enumerates exactly what is returned (total, unseen, recent), so the agent knows the payload shape. It also distinguishes this from a mailbox-selection call. It stops short of naming the nearest sibling (imap_list_mailboxes) as an alternative, which is the only thing separating it from a 5.

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?

'Without selecting it' implies the use case: checking counts for a mailbox the agent does not want to switch into. However, there is no explicit when-to-use versus imap_list_mailboxes, and no stated prerequisite that the mailbox must exist or belong to the given account.

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