Skip to main content
Glama

graph_get_schedule

Retrieve free/busy availability for people or rooms in Microsoft Graph by SMTP address and time window. Use it to find open meeting slots and check schedules before booking.

Instructions

Get free/busy availability for people or rooms.

Args: schedules: List of SMTP addresses (users or rooms) to look up. start_datetime: Start of the lookup window (ISO 8601, e.g. "2025-03-01T09:00:00"). end_datetime: End of the lookup window (ISO 8601). timezone: Timezone for the window (default "UTC"). availability_view_interval: Availability view interval in minutes (default 30). user: Shared or delegated calendar owner address or user ID to act on. Empty targets your own calendar. Requires the delegated Calendars.Read.Shared or Calendars.ReadWrite.Shared permissions.

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": {
      "schedules": "<schedules>",
      "start_datetime": "<start_datetime>",
      "end_datetime": "<end_datetime>"
    },
    "name": "graph_get_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
userNo
timezoneNoUTC
schedulesYes
end_datetimeYes
start_datetimeYes
availability_view_intervalNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does add real behavioral context by disclosing that the `user` parameter requires delegated Calendars.Read.Shared or Calendars.ReadWrite.Shared permissions, but it says nothing about return shape (schedule items / availability view), throttling of free/busy lookups, or whether an empty `user` falls back to the caller's own calendar identity.

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?

Front-loaded with a one-line purpose followed by a compact Args block, so an agent can skim the summary and drop into only the parameter it needs. The docstring wrapper ('Args:') is slightly mechanical but adds no padding.

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?

With no annotations and no output schema, the description is the only source of behavioral information, and it omits the return format entirely — an agent cannot tell whether it receives per-attendee busy blocks, a scheduleId, or an availability-view string. Permission context is handled well, but return-value and throttling information are missing for a tool of this complexity.

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

Parameters4/5

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

Schema coverage is 0%, and the description compensates well by documenting all six parameters, including ISO 8601 format for the datetimes, the default 'UTC' timezone, the default 30-minute interval, and the permission implications of `user`. The one gap is `availability_view_interval`, whose effect on the returned availability view string is not explained, and the schema's meaningless min/max bounds are left unaddressed.

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?

States a specific verb and resource: 'Get free/busy availability for people or rooms,' which is clearly distinct from sibling read tools like graph_get_event or graph_get_meeting_attendance. It stops short of naming an alternative, 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 Guidelines3/5

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

Usage is only implied: the parameter list ('people or rooms', start/end window) suggests a scheduling-availability lookup. There is no explicit when-to-use guidance, no statement of when to prefer graph_get_event, and no note on limits such as maximum schedules per request.

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

Deploy Server

Other Tools