Skip to main content
Glama
new-outlook-mcp

new-outlook-mcp

by michalhron

sync_now

Idempotent

Imports new email and calendar data from local Outlook files into the archive, optionally including configured ICS feeds. Reads copies only and avoids contacting Microsoft servers.

Instructions

Import new mail and calendar data from local Outlook files into the archive. Reads copies of Outlook's files only. The one network access is the user's own published ICS feeds, if configured.

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

Input Schema

NameRequiredDescriptionDefault
sourceNoall

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

The description adds real context beyond the annotations: it clarifies that only copies of local Outlook files are read and that the sole network access is the user's own configured ICS feeds, which explains the openWorldHint=false claim. It does not say what happens to already-archived items on a repeat run or whether duplicates can appear, despite idempotentHint=true.

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 action and its scope front-loaded, followed by the file-access and network caveats. Nothing is redundant or padding.

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?

For a single-parameter sync tool with no output schema, the description covers the purpose and the safety posture, but leaves the source enum unexplained and says nothing about runtime duration or what a sync reports back. Adequate but with a clear gap around the only parameter.

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

Parameters2/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 the parameter meaning, and it largely fails: the opaque enum values 'legacy' and 'hxstore' are never explained, and only 'ics' is loosely covered by the ICS-feed sentence. An agent has no basis to choose a source other than the default 'all'.

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 names a specific verb and resource — importing new mail and calendar data from local Outlook files into the archive — which clearly separates it from the search/read siblings. It stops short of naming any sibling, so differentiation is implied by the write/sync nature rather than stated.

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 only implied: an agent can infer it runs when fresh local Outlook data should be pulled into the archive. There is no explicit when-to-use or when-not-to-use guidance, no prerequisites, and no mention of how it relates to read tools like search_emails for finding the imported data.

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