Skip to main content
Glama

graph_clear_my_presence

Clear your Microsoft Teams presence or undo a preferred presence setting so Teams recalculates your availability.

Instructions

Clear your presence. This is how you undo graph_set_my_presence.

graph_set_my_presence sets a preferred presence, so pass preferred=true to undo it and let Teams calculate your availability again.

Args: preferred: Whether to clear the preferred presence set by graph_set_my_presence (default false clears only this app's session presence).

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

Input Schema

NameRequiredDescriptionDefault
preferredNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it delivers the key behavioral distinction: default clears only this app's session presence, while preferred=true undoes the preferred presence and lets Teams recompute availability. It does not address auth requirements or whether either mode has side effects visible to other users, which keeps it out of the top band.

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

Conciseness4/5

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

The undo relationship is front-loaded in the first sentence, and the Args block earns its space because the schema has no descriptions. There is mild redundancy between "This is how you undo graph_set_my_presence" and the following paragraph restating the same relationship, which could be tightened.

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 single-boolean, single-purpose tool with no annotations and no output schema, the description covers purpose, mutual exclusion with the setter, and both parameter modes. Only peripheral context (permissions, whether Teams presence propagates immediately) is absent.

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% and the schema is a bare boolean with a default, yet the description explains the meaning of both values and what the default does. This is exactly the compensation a low-coverage schema requires.

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?

"Clear your presence" states a specific verb and resource, and the very next sentence frames it as the inverse of graph_set_my_presence, so an agent can distinguish it from graph_set_my_presence / graph_get_my_presence without opening any 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?

It gives an explicit routing rule: to undo graph_set_my_presence pass preferred=true; to clear only this app's session presence leave it default. That covers the main when-to-use decision. It stops short of stating when not to call it (e.g. when another app's session presence is the one active, or verifying with graph_get_my_presence afterward).

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