Skip to main content
Glama

cipp_set_out_of_office

DestructiveIdempotent

Configure out-of-office auto-replies for a mailbox: enable, disable, or schedule replies with custom messages and optional calendar events.

Instructions

⚠ HIGH-IMPACT. Configures the out-of-office / auto-reply for a mailbox, which causes automated messages to be sent to internal and/or external senders. Reversible by disabling the auto-reply. Confirm with the user before invoking.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
upnYesUser Principal Name of the mailbox to configure.
stateYesAuto-reply state. 'Scheduled' replies only between startTime and endTime — useful during offboarding.
endTimeNoWhen the scheduled auto-reply ends — ISO 8601 datetime or Unix epoch seconds. Only valid when state is 'Scheduled'; CIPP defaults to 7 days after startTime if omitted.
timezoneNoTimezone the schedule is interpreted in (e.g. 'Eastern Standard Time'). Requires a recent CIPP build; older ones ignore it.
startTimeNoWhen the scheduled auto-reply starts — ISO 8601 datetime or Unix epoch seconds. Only valid when state is 'Scheduled'; CIPP defaults to now if omitted.
tenantFilterYesTenant domain name or ID to scope the operation. Use 'allTenants' to target every managed tenant.
createOOFEventNoCreate a calendar event covering the out-of-office window. Only valid when state is 'Scheduled'.
externalMessageNoHTML or plain-text auto-reply message sent to senders outside the organisation. Omit to leave the existing message untouched.
internalMessageNoHTML or plain-text auto-reply message sent to senders within the same organisation. Omit to leave the existing message untouched.
oofEventSubjectNoSubject line for the calendar event created by createOOFEvent. Only valid when state is 'Scheduled'.
declineMeetingMessageNoMessage sent when a meeting is declined. Only valid when state is 'Scheduled'.
declineEventsForScheduledOOFNoDecline existing meetings that fall inside the out-of-office window. Only valid when state is 'Scheduled'.
autoDeclineFutureRequestsWhenOOFNoAutomatically decline meeting requests that arrive for the out-of-office window. Only valid when state is 'Scheduled'.
Behavior4/5

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

Annotations already mark the tool as destructive and non-read-only. The description adds value by explaining that it sends automated messages to senders and is reversible, providing practical context beyond annotations.

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

Conciseness5/5

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

Two concise sentences that front-load the warning and state the core action. No wasted words; every sentence earns its place.

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?

Given the tool's complexity (13 params, no output schema), the description is minimal. It covers the essential behavioral impact but lacks details on parameter usage (e.g., scheduling vs immediate). Parameter descriptions compensate somewhat, but completeness is moderate.

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 100%, so baseline is 3. The description does not add meaning beyond the parameter descriptions, which are already detailed. No additional parameter context provided.

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 configures the out-of-office/auto-reply for a mailbox, which is a specific verb and resource. It distinguishes from siblings like set_email_forwarding by focusing on auto-reply functionality.

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 warns of high impact and suggests confirming with the user, but does not explicitly state when to use this tool versus alternatives (e.g., other mailbox or user management tools). Implies caution, not specific use cases.

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/wyre-technology/cipp-mcp'

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