Skip to main content
Glama

graph_set_my_presence

Sets the authenticated user's presence status in Microsoft Teams by choosing availability and activity, with an optional expiration duration.

Instructions

Set the authenticated user's presence status.

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": {
      "availability": "<availability>",
      "activity": "<activity>"
    },
    "name": "graph_set_my_presence"
  }
}

Input Schema

NameRequiredDescriptionDefault
activityYes
availabilityYes
expiration_durationNoPT1H

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden and does not meet it. It never states that this is a state-mutating write, what permissions are required, that presence expires (the PT1H default is only implicit in the schema), or how the previous status is affected.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single grammatical sentence with no filler, so nothing is wasted. However, its brevity comes at the cost of under-specification rather than efficient information density.

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 mutating tool with three completely undocumented parameters, no annotations, and no output schema, the definition provides only the bare purpose. An agent lacks the value domains, permission requirements, and expiry behavior needed to call it reliably.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for three parameters, and the description adds nothing about them. It does not explain valid values for 'availability' or 'activity', nor what 'expiration_duration' means or that it defaults to one hour, leaving every parameter undocumented.

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 ('Set the authenticated user's presence status'), which is clear enough to act on. It does not differentiate from adjacent setters such as graph_set_automatic_replies, graph_set_status_message, or graph_clear_my_presence, so an agent must infer the distinction from names alone.

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, and no reference to graph_clear_my_presence or graph_get_my_presence as alternatives. The agent is left to guess when setting presence is appropriate versus reading or clearing it.

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