Skip to main content
Glama
new-outlook-mcp

new-outlook-mcp

by michalhron

diagnose

Read-onlyIdempotent

Checks Outlook file access, cache layout, archive age, and sync agents when sync fails, results look stale, or a tool errors; returns a fix for each issue.

Instructions

Run when sync fails, results look stale or a tool errors: checks whether this server may read Outlook's files, whether the cache layout matches the decoder, archive age and the sync agents. Each problem comes with a fix to pass on to the user.

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

Input Schema

NameRequiredDescriptionDefault
check_layoutNoAlso decode a copy of the cache to check its layout (slower, about a minute)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds value beyond that by disclosing the diagnostic dimensions and that each finding comes with an actionable fix to relay to the user.

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, trigger condition front-loaded before the list of checks, and the closing clause about fixes earns its place by telling the agent what to do with the output. No filler.

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 no output schema, the description usefully characterizes the return as a set of problems each paired with a fix, which is what an agent needs to act. It leaves the exact output shape and whether the expensive layout check is included by default somewhat implicit, but the essentials are covered.

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 coverage is 100% and the single parameter already documents its cost ('slower, about a minute'). The description adds no further meaning about check_layout, so the baseline of 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 concrete verb with an enumerated scope: it checks Outlook file read permission, cache layout vs decoder, archive age, and sync agents. This is far more specific than a title restatement and makes the tool distinguishable from siblings like archive_status or sync_now.

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

Usage Guidelines4/5

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

Gives explicit triggering conditions ('when sync fails, results look stale or a tool errors'), which is strong when-to-use guidance. It does not name a sibling alternative or say when not to run it, so it stops short of full routing guidance.

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