Skip to main content
Glama
new-outlook-mcp

new-outlook-mcp

by michalhron

list_recent

Read-onlyIdempotent

Lists recent archived emails with optional filters for days, folder, and account to support review of correspondence.

Instructions

List the newest archived emails. freshness and warning work as in search_emails.

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

Input Schema

NameRequiredDescriptionDefault
daysNoOnly messages from the last N days
limitNo
folderNo
accountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds only that results are archived messages returned in newest-first fashion, and omits ordering guarantees, default result count behavior, and what 'archived' excludes. Worse, the second sentence promises `freshness` and `warning` semantics that have no counterpart in this tool's schema, which is misleading behavioral guidance.

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?

Two short sentences with the core purpose front-loaded, so it is efficient in form. However, the second sentence earns no place: it points at parameters absent from the schema and would be better replaced by a line on folder/account filtering or default result count.

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?

For a 4-parameter list tool with no output schema and only 25% schema coverage, the definition leaves too much unstated: default limit of 20 and the 200 cap, what folder/account accept, whether archived is assumed, and what the response contains. The dangling `freshness`/`warning` reference adds confusion rather than completeness.

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

Parameters1/5

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

Schema description coverage is only 25% — `days` is documented but `limit`, `folder`, and `account` are not — so the description needed to compensate and does not. Instead it references `freshness` and `warning`, parameters that do not exist in this schema, actively misdirecting the agent while leaving the real filters unexplained.

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 opening sentence names a specific verb and resource ('List the newest archived emails'), which distinguishes it from the broader sibling search_emails by scoping results to archived mail and to recency order. It stops short of a 5 because it never states how 'newest' is bounded or how this differs operationally from a date-sorted search.

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 explicit when-to-use or when-not-to-use guidance; the agent must infer that this is the browse-recent-archive path versus search_emails. The only routing signal is the cross-reference 'work as in search_emails', which describes parameter behavior rather than tool selection.

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