Skip to main content
Glama

mail_list

Read-only

List the newest messages in a specified Outlook folder, optionally filtering unread only or by a since date.

Instructions

List the newest messages in a folder. folder is a well-known name (inbox, sentitems, drafts, archive, deleteditems, junkemail) or an id from mail_folders. since is an ISO date or date-time such as 2026-11-01, in the server's time zone unless it has an offset.

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

Input Schema

NameRequiredDescriptionDefault
topNo
sinceNo
folderNoinbox
unread_onlyNo

Output Schema

NameRequiredDescriptionDefault
resultYes

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?

The annotations already declare readOnlyHint and openWorldHint, so the description does not need to explain safety. It adds useful behavior around ordering ('newest'), accepted folder names, and time-zone handling for `since`. It omits the default result limit (`top`) and the meaning of `unread_only`, which are relevant list behaviors.

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?

The description is short, front-loaded with the primary action, and free of filler. Every sentence adds something useful about scope, folder identifiers, or date filtering.

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?

An output schema exists, so return values need not be described, and the tool is conceptually simple. The description covers the non-obvious folder and date semantics well. It is still incomplete for a zero-coverage schema because it says nothing about the default `top` limit or `unread_only` filtering.

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 0%, so the description must carry parameter meaning. It explains `folder` in detail and clarifies `since` as an ISO date or date-time with explicit time-zone semantics, which is valuable. It does not document `top` or `unread_only` at all, leaving half the parameters to inference.

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 states a specific verb and resource: 'List the newest messages in a folder.' That clearly distinguishes a folder listing from siblings like mail_get or mail_search. It does not explicitly name or position itself against those alternatives, which keeps it just short of 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?

Usage is implied by 'List the newest messages in a folder,' and the description explains where folder identifiers come from. However, it gives no explicit when-to-use guidance versus mail_search or other retrieval tools, and no exclusions or prerequisites.

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