Skip to main content
Glama

Mail Get Emails

mail_get_emails

List emails from a chosen mailbox with filters for unread, flagged, today, or last 7 days and a result limit. Returns messages disk-first without a full scan, so mailbox lookups stay quick.

Instructions

List emails from one mailbox (disk-first, no full scan).

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

Input Schema

NameRequiredDescriptionDefault
limitNo
filterNoall
accountNo
mailboxNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. "Disk-first, no full scan" is the only behavioral hint and it is ambiguous jargon – it could mean cached/stale results, bounded cost, or a fast path, but the reader cannot tell which, and nothing says whether it is read-only, paginated, or what the default ordering is.

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

Conciseness3/5

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

A single short sentence with the resource front-loaded and no filler. However, brevity here is under-specification, not efficiency: the parenthetical jargon consumes the only clause that could have explained behavior.

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

Completeness2/5

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

A four-parameter list tool with no output schema and no annotations needs the description to cover filtering, default result size, and return shape. None of that is present, so an agent must open the schema and guess at semantics before calling it.

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% across four parameters, yet the description never mentions limit, filter, account, or the enum values (unread/flagged/today/last_7_days). "One mailbox" weakly implies the mailbox parameter exists but adds no format, default, or interaction semantics to compensate for the coverage gap.

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?

"List emails from one mailbox" gives a specific verb (list) plus resource (emails) and a scope (single mailbox), which is enough to separate it from the mutation siblings. It does not explicitly contrast with mail_search, so the agent must infer that this is the plain enumeration path rather than query-based retrieval.

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 statement of when to prefer this over mail_search or mail_get_email, nor any prerequisite or exclusion. The phrase "from one mailbox" hints at scope but the mailbox parameter is optional with a null default, so the implied guidance is not even consistent with the schema.

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