Skip to main content
Glama

graph_get_user_presence

Fetch a user's presence status by ID to determine availability for messaging, calls, or meetings.

Instructions

Get another 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": {
      "user_id": "<user_id>"
    },
    "name": "graph_get_user_presence"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

C2.9/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 it says essentially nothing beyond the name. It does not mention required permissions (presence read scope), whether the target user must be in the same tenant, rate limits, or what the presence status comprises (availability/activity).

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?

A single tight sentence with no filler and the key distinguishing word ('another') front-loaded. It is concise but the brevity is achieved by omitting information rather than by efficient phrasing of rich content.

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?

With no annotations and no output schema, the description must explain both the identifier format and the shape/meaning of the returned presence data; it does neither. For a permission-gated cross-user read this leaves an agent guessing about access requirements and result interpretation.

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

Parameters2/5

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

Schema coverage is 0% and the description does not mention the single parameter at all. It gives no hint whether user_id expects an object ID, UPN, or email, nor any behavior for unknown or malformed users, so nothing is added beyond the bare schema type.

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?

Clear verb+resource: 'Get' a 'presence status' for 'another user'. The word 'another' usefully separates it from graph_get_my_presence, though no sibling is named explicitly and the batch variant graph_get_presences_by_user_ids is not acknowledged.

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?

Usage is only implied by 'another user's' — that phrasing suggests it is for someone other than the caller, which contrasts with a my-presence tool. There is no explicit when-to-use/when-not, no guidance on choosing the batch-by-ids sibling, and no prerequisites stated.

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