Local MCP

Outlook Diagnose

outlook_diagnose

Read-only

Checks which email accounts are configured in Microsoft Outlook and compares them with Mail.app. If Outlook has accounts not in Mail.app, guides the user to add them so all email tools work seamlessly.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`note`	No	Plain-language guidance
`report`	No	Full formatted text report
`installed`	Yes	True if Microsoft Outlook is installed
`mail_app_error`	No	Non-empty when Mail.app accounts could not be read (e.g. Automation permission denied/not determined) — an empty mail_app_accounts then means 'couldn't check', not 'zero accounts'
`outlook_accounts`	No
`mail_app_accounts`	No
`missing_from_mail_app`	No	Outlook account emails not present in Mail.app

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 5, 2026

addedOutput schema / properties / mail_app_error

Added value: +{
+  "description": "Non-empty when Mail.app accounts could not be read (e.g. Automation permission denied/not determined) — an empty mail_app_accounts then means 'couldn't check', not 'zero accounts'",
+  "type": "string"
+}

First observedJun 30, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the text is consistent with that (it 'guides' rather than performs changes). It adds genuine behavioral context beyond the annotations: it compares two account stores and produces remediation guidance, which is not visible from structured fields. It does not disclose failure modes if Outlook is unconfigured, keeping it from a 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 sentences, front-loaded with the core action and followed by the conditional outcome. No filler or repetition of the title.

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

Completeness4/5

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

With zero parameters and an output schema present, the description does not need to explain return values, and it covers the tool's purpose and follow-up behavior adequately. Minor gap: no mention of prerequisite state (Outlook installed/configured) or what happens when no discrepancy exists.

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

Parameters4/5

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

The tool takes no parameters, so there is no argument semantics to explain — baseline 4 applies. The description correctly adds no spurious parameter talk.

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?

Names a specific verb (checks/compares) and resource (Outlook email accounts vs Mail.app), so an agent can tell it apart from plain listing tools like list_email_accounts. It does not explicitly name the sibling alternatives (list_email_accounts, configure_clients), so it stops 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?

The description implies the diagnostic scenario (accounts missing in Mail.app) and the subsequent remediation, which suggests when the tool matters. However it never states when to choose this over list_email_accounts or run_diagnostics/lmcp_doctor, or any prerequisite about Outlook being installed. Implied usage only.

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.