Skip to main content
Glama

graph_update_mailbox_settings

Update your own mailbox time zone and working hours while leaving unspecified settings unchanged; only supplied fields are modified.

Instructions

Update the mailbox time zone and working hours.

Only the parts you supply are sent, so the rest of the mailbox settings stay as they are. This always targets your own mailbox: Graph exposes no shared variant of mailbox settings.

Args: time_zone: Mailbox time zone name (e.g. "Pacific Standard Time"). working_days: Working days, lowercase (e.g. ["monday", "tuesday"]). working_hours_start: Start of the working day (e.g. "09:00:00"). working_hours_end: End of the working day (e.g. "17:00:00"). working_hours_timezone: Time zone name for the working hours.

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_update_mailbox_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
time_zoneNo
working_daysNo
working_hours_endNo
working_hours_startNo
working_hours_timezoneNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does a good job on the most important trait: 'Only the parts you supply are sent, so the rest of the mailbox settings stay as they are' clearly documents partial-update semantics rather than full replacement. It also discloses the self-mailbox-only targeting, though it omits permission requirements and what happens with an invalid time zone or day name.

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?

Front-loads the action and the two most consequential facts (partial update, own mailbox only) before dropping into a compact Args list. Every sentence adds information; nothing restates the tool name or pads the text.

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?

Five parameters at 0% schema coverage, no annotations, and no output schema — the description covers the update semantics, the targeting constraint, and all parameter formats, which is most of what an agent needs. It falls short only on prerequisites (required scopes) and error/validation behavior.

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 description coverage is 0%, so the description must compensate, and it documents all five parameters with concrete examples and format cues ('Pacific Standard Time', lowercase day names, '09:00:00' / '17:00:00'). What it does not supply is the closed set of valid day names or where to obtain valid time zone identifiers, leaving some ambiguity for an agent constructing values.

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 ('Update the mailbox time zone and working hours') and narrows the scope to exactly two settable areas, which cleanly separates it from graph_get_mailbox_settings. It does not name the read sibling explicitly, so the differentiation is implied by the verb rather than spelled out.

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?

Provides a real scoping constraint — 'This always targets your own mailbox: Graph exposes no shared variant of mailbox settings' — which tells the agent there is no target-user parameter to look for. However, it never says when to prefer this over graph_get_mailbox_settings or what to do first (e.g. read settings before patching), so usage is mostly implied.

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