Skip to main content
Glama
new-outlook-mcp

new-outlook-mcp

by michalhron

find_free_slots

Read-onlyIdempotent

Find available time blocks of a given length in your Outlook calendar, filtered by date range, working hours, weekdays, and timezone.

Instructions

Find free slots of a given length in my own calendar.

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": {
      "duration_minutes": "<duration_minutes>",
      "start": "<start>"
    },
    "name": "find_free_slots"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo
startYes
timezoneNoIANA timezone for input and output times (default: this Mac's zone)
weekdaysNoMO-FR
max_resultsNo
step_minutesNo
working_hoursNo09:00-17:00
duration_minutesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so safety is covered. The description contributes the useful scope fact that only the owner's calendar is searched, but says nothing about how slots are derived (working hours, weekday filter, step granularity) or whether results are capped. Modest added context on top of already-rich annotations.

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 with the scope constraint front-loaded and no filler. It is cleanly written; the only knock is that it is short to the point of under-specification given eight parameters, though brevity itself is not a fault.

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

Completeness2/5

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

For an eight-parameter scheduling tool with no output schema and near-zero schema description coverage, one sentence leaves too much unspecified: default working hours, weekday format, step size semantics, result cap behavior, and open-ended vs bounded search are all unexplained. The agent can form no expectation of the returned shape (list of intervals? start/end objects?).

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 13% — just the timezone parameter is documented — and 6 of 8 parameters (weekdays, working_hours, step_minutes, max_results, start, end) carry no explanation anywhere. The description's "of a given length" loosely maps to duration_minutes but gives no help on the free-form string formats "09:00-17:00" and "MO-FR" or on the meaning of a null end.

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 uses a specific verb+resource ("Find free slots") and adds a scoping qualifier ("in my own calendar") plus the length constraint, so the agent knows this is single-calendar availability lookup. It stops short of distinguishing itself from the sibling calendar_freebusy, but the purpose itself is unambiguous.

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

Usage Guidelines2/5

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

There is no when-to-use/when-not-to-use guidance and no mention of the obvious alternative (calendar_freebusy) or of prerequisites. The phrase "my own calendar" implies a scope limit but never states that other people's availability requires a different tool.

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