Skip to main content
Glama

graph_get_mailbox_settings

Retrieve mailbox settings—automatic replies, time zone, and working hours—for your own or a colleague's mailbox to review availability and out-of-office configuration.

Instructions

Get mailbox settings, including automatic replies, time zone, and working hours.

Args: user: Colleague's address or user ID whose settings to read. Empty targets your own mailbox. Reading someone else needs delegate rights on that mailbox plus the MailboxSettings.Read permission.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "graph_get_mailbox_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
userNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the authorization prerequisites (delegate rights, MailboxSettings.Read) and the default-targeting behavior of an empty parameter. It omits failure behavior and any pagination/shape notes, but the field enumeration covers the main return content.

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?

Three short sentences, front-loaded with the purpose, then the parameter meaning and the permission caveat. No filler or restated boilerplate.

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

Completeness5/5

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

For a single-parameter read tool with no annotations and no output schema, the definition covers purpose, parameter semantics, authorization requirements, and the fields returned — everything an agent needs to call it correctly.

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%, yet the description fully explains the single parameter: accepted forms (address or user ID), the empty-string default meaning (own mailbox), and the permission implications of cross-mailbox reads.

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 ('Get') and resource ('mailbox settings') and enumerates the contents (automatic replies, time zone, working hours). This clearly separates it from the update sibling (graph_update_mailbox_settings) without needing the schema opened.

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 usage context: an empty user targets your own mailbox, while reading a colleague's requires delegate rights plus MailboxSettings.Read. It does not name alternatives or state when not to use it, so it falls short of a 5.

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