Skip to main content
Glama

ews_suggest_slots

Suggest overlapping free meeting slots for multiple attendees and optional candidate rooms within a specified date and time range.

Instructions

Suggest nearest overlapping free meeting slots for multiple attendees and optional candidate meeting rooms. Omits workday_start, workday_end, and avoid to use local policy defaults.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
attendeesYes
startYesISO datetime with timezone
endYesISO datetime with timezone
roomsNoCandidate meeting rooms. Supports aliases like 2-11, 2-13, 2-14, 3-1, 3-2, 3-4.
require_roomNoWhen true and rooms is empty, search Exchange room lists when available, then fall back to configured static rooms and filter by capacity.
duration_minutesNo
limitNo
workday_startNoHH:MM. Omit to use local policy default.
workday_endNoHH:MM. Omit to use local policy default.
avoidNoHH:MM-HH:MM ranges. Omit to use local policy default.
Behavior3/5

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

No annotations are provided, so the description bears full burden. It mentions using local policy defaults for workday_start, workday_end, and avoid, but lacks details on time zone handling, error conditions, or performance traits.

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?

The description is concise (two sentences) and front-loaded with the main purpose. It could be slightly more structured but is effective.

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?

With 10 parameters and no output schema, the description is insufficient. It does not explain return format, how conflicts are resolved, or what 'nearest overlapping' means in practice.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 70%, so parameter descriptions exist. The description adds context about defaulting omitted parameters to local policy, but does not significantly extend beyond the schema.

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?

The description clearly states the tool suggests nearest overlapping free meeting slots for multiple attendees and optional rooms, which distinguishes it from siblings like ews_get_free_busy or ews_find_calendar_events.

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?

The description implies usage for finding free slots but does not explicitly state when to use this tool over alternatives, nor does it provide exclusions or when-not scenarios.

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/ap311036/ews-meeting-mcp'

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