Skip to main content
Glama
new-outlook-mcp

new-outlook-mcp

by michalhron

search_calendar

Read-onlyIdempotent

Search calendar events by keyword across subjects, locations, people, and bodies, with optional date ranges and result limits to find relevant meetings.

Instructions

Search calendar events.

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": {
      "query": "<query>"
    },
    "name": "search_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesFull-text query over subject, location, people and body
date_toNo
timezoneNoIANA timezone for input and output times (default: this Mac's zone)
date_fromNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds nothing beyond that: it does not say whether results are capped, how they are ordered, or what a query matches. A single unadorned sentence leaves the behavioral burden entirely on the annotations.

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

Conciseness3/5

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

It is a single short sentence with zero waste, and the core purpose is front-loaded. But the brevity comes from omission rather than discipline — the sentence is too thin for a 5-parameter search tool with a date range and pagination.

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 search tool with no output schema, the definition is technically callable but under-specified. With five parameters at 40% schema coverage and no return-value description, the agent cannot tell how results are shaped, ordered, or bounded.

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 coverage is only 40%, and the description supplies no parameter meaning at all. The two coupled fields query and timezone are documented in the schema, but date_from, date_to, and limit are opaque — the description never explains that the dates bound the search window or that limit caps 50 by default up to 200.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Search calendar events" names a verb and a resource, so the basic purpose is clear. But it gives no scope (all events vs. a range, which fields are matched) and does nothing to distinguish itself from siblings like list_calendar_events, calendar_freebusy, or get_calendar_event. An agent must open the schema to learn the query covers subject/location/people/body.

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 guidance on when to use this tool rather than a sibling — nothing tells the agent to prefer list_calendar_events for browsing or calendar_freebusy for availability. No prerequisites, no exclusions, no mention of pagination or date-range behavior.

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