Skip to main content
Glama

graph_get_presences_by_user_ids

Retrieves Microsoft Graph presence for up to 650 users in one round trip. Use it to fetch availability for many people at once instead of calling the single-user presence tool per person.

Instructions

Get presence for up to 650 users in one round trip.

Use this instead of calling graph_get_user_presence once per person. Needs the Presence.Read.All permission.

Args: user_ids: User IDs to look up (1-650 per call).

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_ids": "<user_ids>"
    },
    "name": "graph_get_presences_by_user_ids"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the key operational facts: a hard batch ceiling of 650, a single round trip, and the Presence.Read.All permission requirement. It stops short of describing the response shape or what happens for IDs that resolve to no presence data, which matters since there is no output schema.

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 the capability and scale, followed by the sibling-routing instruction and the permission note. Three short lines, no filler; the Args block is minimal but not padded.

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-parameter batch read with no annotations and no output schema, the definition supplies the essentials an agent needs to select and invoke it correctly: batching rationale, size limit, and auth requirement. The missing piece is a one-line sketch of the returned presence data.

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?

Only one parameter and schema coverage is 0%, so the description must compensate. It identifies the parameter as user IDs to look up and notes the per-call range; the 1-650 bounds largely duplicate minItems/maxItems, but the semantic framing of what to supply is useful. It does not clarify ID format (UPN vs object ID), which is the main remaining gap.

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 (get), resource (presence), and scale (up to 650 users in one round trip). It explicitly contrasts with graph_get_user_presence, so an agent can route without opening either schema.

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?

Gives an explicit alternative and the condition that selects it: 'Use this instead of calling graph_get_user_presence once per person.' The batching intent is unambiguous.

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