Skip to main content
Glama
Sign In
Enterprise Microsoft 365 MCP Server

Enterprise Microsoft 365 MCP Server

by ManoAlee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

m365_configure_vacation

Configure scheduled out-of-office auto-replies with HTML formatting and optional forwarding or redirection for Microsoft 365 mailboxes.

Instructions

Configures scheduled out-of-office auto-reply with HTML formatting and optional forwarding/redirection.

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": {
      "user_upn": "<user_upn>",
      "start_date": "<start_date>",
      "end_date": "<end_date>",
      "return_date": "<return_date>",
      "signature_name": "<signature_name>"
    },
    "name": "m365_configure_vacation"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateYes
user_upnYes
start_dateYes
redirect_toNo
return_dateYes
signature_nameYes
inform_team_handlingNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries full behavioral burden. It hints that HTML formatting and forwarding/redirection are supported, but says nothing about whether existing settings are overwritten, what permissions are required, or reversibility – significant gaps for a mutation tool.

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?

A single efficient sentence with the core purpose front-loaded and no filler. Its brevity is appropriate structurally even though the content is thin elsewhere.

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?

For a 7-parameter mutation tool with 5 required fields, no annotations, and 0% schema description coverage, the description is far too sparse. An output schema exists so return values need not be explained, but the input semantics and behavioral effects are left largely uncovered.

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 description coverage is 0%, so the schema explains none of the 7 parameters. The description alludes to forwarding/redirection (mapping loosely to redirect_to) but leaves user_upn, start_date, end_date, return_date, signature_name, and inform_team_handling entirely unexplained.

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?

The verb 'Configures' plus resource 'out-of-office auto-reply' is specific and identifies the operation clearly. It does not explicitly distinguish itself from close siblings like m365_disable_vacation or m365_get_vacation_status, but the intent 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 Guidelines2/5

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

There is no when-to-use guidance, no mention of prerequisites (permissions, mailbox targeting), and no reference to the sibling status/disable tools. The agent must infer usage from the name alone.

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