Local MCP

Microsoft 365 List Emails

m365_list_emails

Read-only

Use this when the user wants their Microsoft 365 / Outlook / Exchange inbox via the cloud — requires a connected M365 account (connect_m365_account). Returns subject, sender, date, and preview. For mail already in the Mac's Mail.app (including an Exchange account added there), use list_emails.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Number of emails to return (default 20, max 50)
`folder`	No	Folder name: inbox (default), sentitems, drafts, deleteditems
`account`	No	Which connected Microsoft 365 account to use: its email (UPN), its id from list_m365_accounts, or its display name when unique. Leave it out to use the default account.
`unread_only`	No	If true, return only unread emails

Output Schema

TableJSON Schema

Name	Required	Description
`count`	No
`emails`	No
`account`	No	The email (UPN) of the Microsoft 365 account this call used.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 5, 2026

addedInput schema / properties / account

Added value: +{
+  "description": "Which connected Microsoft 365 account to use: its email (UPN), its id from list_m365_accounts, or its display name when unique. Leave it out to use the default account.",
+  "type": "string"
+}

addedOutput schema / properties / account

Added value: +{
+  "description": "The email (UPN) of the Microsoft 365 account this call used.",
+  "type": "string"
+}

First observedJun 30, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds real context beyond that: the account-connection prerequisite and the shape of the returned fields. It stops short of noting rate limits, pagination, or token/scope requirements, so a 4 rather than 5.

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 tight sentences with the use case front-loaded, followed by the routing rule to the sibling. Every clause carries information (platform, prerequisite, return fields, alternative) with no filler.

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?

For a read-only listing tool with full schema coverage, annotations, and an output schema, the description supplies everything the agent still needs: when to pick it, the connection prerequisite, and the disambiguation from list_emails. Return-value explanation is redundant given the output schema but harmless.

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%, so the schema already documents limit, folder, account, and unread_only with defaults and formats. The description adds no parameter-level detail (e.g. folder semantics or account resolution) beyond what the schema states, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (list emails) and pins the exact backend (Microsoft 365 / Outlook / Exchange via the cloud). It also implicitly differentiates from the Mac-local tool by naming that counterpart, so an agent can route without opening either schema.

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

Usage Guidelines5/5

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

Explicitly gives the use condition ('when the user wants their M365/Outlook/Exchange inbox via the cloud'), states the prerequisite (a connected M365 account via connect_m365_account), and names the alternative 'list_emails' for the Mac Mail.app case with the discriminating condition. Nothing is left to inference.

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

All Local MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.