Skip to main content
Glama
marlonluo2018

Microsoft Graph MCP Server

user_settings

Initialize or update user settings for email search parameters, page sizes, and multimodal capability.

Instructions

Manage user settings with two actions: 'init' to initialize settings when configuration is missing or corrupted (requires multimodal_supported parameter to indicate if LLM supports image processing), 'update' to update one or more settings (supports partial updates). Note: 'init' action attempts to get user timezone from Graph API if authenticated, but works without login. 'update' action is purely local and requires no authentication. MULTIMODAL DETECTION: If you are a multimodal LLM that can process images, please set multimodal_supported=true when calling init or update.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform: 'init' to initialize settings when configuration is missing (requires multimodal_supported), 'update' to update one or more settings (partial update supported)
timezoneNoUser timezone in IANA format. Examples: 'America/New_York', 'Asia/Shanghai', 'Europe/London', 'UTC'. Only used with 'update' action.
page_sizeNoPage size for user browsing (default: 5, recommended range: 3-10). Only used with 'update' action.
llm_page_sizeNoPage size for LLM browsing (default: 20, recommended range: 10-50). Only used with 'update' action.
max_search_daysNoMaximum allowed search range in days (default: 90). Only used with 'update' action.
default_search_daysNoDefault number of days to search for emails when not specified (default: 7). Only used with 'update' action.
multimodal_supportedNoSet to true if the LLM supports multimodal capabilities (can process images). Used with both 'init' and 'update' actions. When true, email image attachments will include base64 content for the LLM to analyze.
Behavior5/5

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

No annotations are provided, so the description must disclose all behavioral traits. It does so comprehensively: explains that 'init' may attempt Graph API but works without login, 'update' is local and requires no auth, and includes a multimodal detection directive. No contradictions.

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?

The description is well-structured with clear sections and no redundant sentences. It efficiently covers purpose, usage, parameter context, and behavioral notes without being verbose.

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?

Given the tool's complexity (two actions, multiple parameters, auth context, no output schema), the description fully equips an agent to select and invoke correctly. It covers all necessary details: action selection, parameter applicability, authentication nuances, and a multimodal detection note.

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 coverage is 100%, so baseline is 3. The description adds significant context by grouping parameters under actions and explaining the multimodal_supported parameter's role for LLMs, which goes beyond schema descriptions. However, it does not elaborate on parameter formats beyond what the schema provides, so not a 5.

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 manages user settings with two distinct actions: 'init' for initialization and 'update' for modifications. It uniquely identifies each action's purpose and resource, and no sibling tool overlaps, ensuring clarity.

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

Usage Guidelines5/5

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

Explicit guidance on when to use each action: 'init' when configuration is missing or corrupted, 'update' for partial updates. It also clarifies authentication requirements and the multimodal_supported parameter, leaving no ambiguity.

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/marlonluo2018/microsoft_graph_mcp_server'

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