Skip to main content
Glama
new-outlook-mcp

new-outlook-mcp

by michalhron

calendar_freebusy

Read-onlyIdempotent

Find your own busy blocks and free time within working hours for a date range; other people's calendars are not included.

Instructions

My own busy blocks and free time within working hours. Other people's calendars are not available.

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

Input Schema

NameRequiredDescriptionDefault
endNo
startYes
timezoneNoIANA timezone for input and output times (default: this Mac's zone)
weekdaysNoe.g. MO-FR or MO,TU,THMO-FR
working_hoursNoe.g. 09:00-17:0009:00-17:00
include_tentativeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that results are constrained to the caller's own calendar and to working hours, which is genuine behavioral context, but it says nothing about the shape of the returned blocks or how weekdays and tentative events affect output.

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?

Two short sentences with the core capability front-loaded and the scope limit immediately after; nothing is wasted. It is arguably under-written for a 6-parameter tool, but that is a completeness issue rather than verbosity.

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 read-only availability query with no output schema, the agent knows roughly what comes back (busy blocks and free time) and that it is limited to the caller's calendar. Missing are the accepted time format for start/end, how the working-hours and weekdays defaults trim the result, and whether tentative events are included by default.

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?

With 6 parameters and only 50% schema description coverage, the description needs to carry weight but mostly does not. 'Within working hours' loosely gestures at working_hours and weekdays, while start, end, timezone and include_tentative get no meaning from the description at 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 the specific resource: the caller's own busy blocks and free time, restricted to working hours. That is concrete and distinguishable from a generic calendar query, but it never names or contrasts with the sibling find_free_slots, which sounds like it answers an overlapping question.

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 a hard scope statement ('Other people's calendars are not available'), which is a useful exclusion, but no guidance on when to pick this over find_free_slots or list_calendar_events. The agent must infer usage from the noun phrase alone.

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