Skip to main content
Glama
mpalermiti

outlook-mcp

by mpalermiti

outlook_changes_since

Retrieve a unified digest of changes since the last call: new and urgent flagged mail, top senders, and new or cancelled events and contacts. Supports delta tokens for incremental updates.

Instructions

One structured "since last call" digest across mail, events, and contacts.

Use this for recurring agent loops (morning brief, hourly inbox sweep) — one call returns counts, urgent_flagged mail, by-sender rollup, plus new/cancelled events and contacts counts. Use the three individual delta tools (outlook_list_inbox_delta, outlook_list_events_delta, outlook_list_contacts_delta) when you need raw item lists or per-resource control.

Example: first call: outlook_changes_since(); next: outlook_changes_since(delta_tokens=). First call returns a snapshot filtered to the last fallback_window_hours (default 24) so the digest doesn't surface thousands of historical items; subsequent calls (tokens passed back) return only what changed. Each resource's token is independent — drop one stale token without re-syncing the others. If Graph 410s on a token (syncStateNotFound), that resource auto-resyncs and _meta.resync lists which one. urgent_flagged = high-importance OR flagged mail. by_sender = top 5 senders. Calendar modified[] is reserved for future use — modified events surface in new[] today (Graph delta doesn't distinguish them). Calendar organizer_email is also currently empty (the v1.9.0 delta formatter surfaces the organizer name only).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
delta_tokensNo
fallback_window_hoursNo
Behavior5/5

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

No annotations provided, but description thoroughly discloses behavioral traits: first call snapshot with fallback window, token-based incremental updates, independent tokens, auto-resync on 410, definitions of urgent_flagged and by_sender, and known limitations (modified[] reserved, organizer_email empty).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Long but information-dense description. Front-loaded with purpose, then usage, then details. Every sentence adds value, but could be slightly more concise without losing clarity.

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?

No output schema, but description explains key output elements: counts, urgent_flagged, by_sender, new/cancelled events/contacts, and _meta.resync. Lacks exact structure but adequate for understanding.

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?

Schema coverage is 0%, but description adds meaning to both parameters: delta_tokens are from prior response and independent per resource; fallback_window_hours defaults to 24 and filters historical items. Does not specify exact structure of delta_tokens object but context is sufficient.

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?

Clearly states it provides a structured digest across mail, events, and contacts, with a specific verb 'digest' and distinguishes from sibling individual delta tools.

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 says when to use (recurring agent loops) and when to use alternatives (individual delta tools for raw lists). Includes an example of first and subsequent calls.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mpalermiti/outlook-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server