Skip to main content
Glama
new-outlook-mcp

new-outlook-mcp

by michalhron

meeting_prep

Read-onlyIdempotent

Gathers event details, attendees, and recent email threads so you can prepare for a meeting with context and useful talking points.

Instructions

Prepare for a meeting: event details, attendees, and recent email threads with them or on the topic.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "event_id": "<event_id>"
    },
    "name": "meeting_prep"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYes
timezoneNoIANA timezone for input and output times (default: this Mac's zone)
days_backNo
max_threadsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description usefully discloses that this is an aggregator spanning calendar and mail data ('threads with them or on the topic'), which is more than the annotations say. It omits the implicit 90-day lookback window, the thread cap, and what happens if the event has no matching threads.

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?

A single compact sentence, front-loaded with the goal and then the payload. Nothing is wasted, though the brevity comes at the cost of the parameter detail noted above.

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?

For a read-only four-parameter aggregator with no output schema, the description does state the return contents (event details, attendees, threads), which substitutes reasonably for a schema. The remaining gap is the two undocumented numeric tuning parameters, which an agent could easily set wrongly.

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 only 25% – timezone is the sole documented parameter, while event_id, days_back and max_threads carry no schema description. The description says 'recent email threads' but never ties that to the days_back or max_threads controls, so the agent gets no guidance on how far back it searches or how results are capped. With low coverage the description needed to compensate and does not.

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-plus-goal ('Prepare for a meeting') and enumerates the three things it assembles: event details, attendees, and recent email threads. That composite nature distinguishes it from single-resource siblings like get_calendar_event or search_emails, though it never explicitly contrasts itself with them.

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 by the phrase 'Prepare for a meeting' – the agent can infer it is a pre-meeting aggregation call. There is no explicit statement of when to prefer this over chaining get_calendar_event plus search_emails, and no note about prerequisites such as needing a valid event_id from a calendar listing.

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