Skip to main content
Glama

graph_set_status_message

Set your Microsoft Teams status message, including optional expiry and timezone, to display a note under your name.

Instructions

Set your Teams status message, the note shown under your name.

This is separate from availability, which graph_set_my_presence controls.

Args: message: The status message text. expiry_datetime: Optional expiry in ISO 8601 (e.g. "2026-03-01T17:00:00"). Empty means the message does not expire. timezone: Timezone for expiry_datetime (default "UTC").

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": {
      "message": "<message>"
    },
    "name": "graph_set_status_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYes
timezoneNoUTC
expiry_datetimeNo

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?

No annotations are supplied, so the description carries the full burden. It does well on expiry semantics (empty means no expiry, default timezone UTC, ISO 8601 format), but says nothing about permissions/auth required, whether an existing status message is overwritten, or what the call returns on success.

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-loaded with purpose and the key disambiguation, then a compact Args block that carries information the schema lacks. No redundant or filler sentences.

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 a 3-parameter mutation tool with no annotations and no output schema, the description covers purpose, the sibling boundary, and every parameter's meaning. The remaining gap is behavioral: auth requirements and overwrite/return behavior are unaddressed.

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 does: all three parameters are explained, including the ISO 8601 example for expiry_datetime, the empty-string sentinel meaning 'no expiry', and the UTC default for timezone. It loses a point only for not stating any content limits on the message text or noting that timezone is irrelevant when no expiry is set.

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 and resource ('Set your Teams status message') and immediately explains the resource in user terms ('the note shown under your name'), then contrasts it with the availability concept controlled by graph_set_my_presence. An agent can distinguish this from presence-setting without opening the schema.

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?

The second sentence gives a clear usage boundary: this is not availability, and graph_set_my_presence is the sibling for that. It stops short of explicit when-not conditions (e.g., do not use for auto-replies, use graph_set_automatic_replies) but the primary ambiguity is resolved.

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