Skip to main content
Glama

graph_set_automatic_replies

Set or clear out-of-office automatic replies, including scheduled windows, internal and external messages, and audience targeting.

Instructions

Set or clear the automatic reply (out of office) message.

Args: status: "disabled", "alwaysEnabled", or "scheduled". Scheduled requires start_datetime and end_datetime. internal_message: Reply sent to people inside the organization. When is_html is true, send explicit HTML; markdown is not converted. external_message: Reply sent to people outside the organization. Empty reuses internal_message. external_audience: Who outside the organization receives a reply: "none", "contactsOnly", or "all" (default "none"). start_datetime: Scheduled window start (ISO 8601, e.g. "2025-03-01T09:00:00"). end_datetime: Scheduled window end (ISO 8601). timezone: Timezone for the scheduled window (default "UTC"). is_html: Whether the messages are HTML content (default: True). Use false for plain text.

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": {
      "status": "<status>"
    },
    "name": "graph_set_automatic_replies"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusYes
is_htmlNo
timezoneNoUTC
end_datetimeNo
start_datetimeNo
external_messageNo
internal_messageNo
external_audienceNonone

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description must carry the whole burden. It does disclose real behavior beyond the schema: HTML is sent as-is with no markdown conversion, external_audience defaults to 'none', and an empty external_message falls back to internal_message. It omits, however, whether 'disabled' wipes stored messages, what permissions are required, and whether the operation is reversible.

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 summary sentence is front-loaded and the per-argument breakdown is scannable, but it restates defaults that already exist in the schema (timezone UTC, is_html true, external_audience 'none'), which adds some redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an eight-parameter mutation tool with no annotations and no output schema, argument coverage is thorough. The remaining gap is outcome behavior — whether clearing removes prior messages and what the call returns — which matters because there is no output schema to document the response.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate, and it does — all eight parameters are explained with defaults, allowed enum values, ISO 8601 format with an example, and cross-parameter dependencies. This is meaningfully more than the bare types in 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?

States a specific verb ('Set or clear') and resource ('automatic reply (out of office) message'), and the parenthetical makes the concept unambiguous. No sibling in the provided list offers an overlapping capability, so an agent can immediately tell this is the sole tool for OOO settings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives concrete conditional rules rather than vague hints: 'Scheduled requires start_datetime and end_datetime' and 'Empty reuses internal_message.' It stops short of explicit when-to-use/when-not guidance (e.g., what happens to existing messages when status is 'disabled'), but there is no competing tool to route against.

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