Skip to main content
Glama

graph_list_rooms

Lists bookable meeting rooms in a tenant and returns email addresses for checking availability or booking rooms as event attendees.

Instructions

List bookable meeting rooms in the tenant.

Requires the delegated Place.Read.All permission. Use the returned email addresses with graph_get_schedule to check availability, or as attendees on graph_create_event to book a room.

Args: room_list: Room list email address to list rooms from. Empty lists every room in the tenant. top: Maximum number of rooms to return (default 50, maximum 50). skip: Number of items to skip before returning results (default 0). Graph returns at most 50 per call, so page by raising skip in steps of top. next_link: Opaque nextLink URL from a previous call, used to fetch the next page. Overrides the other paging arguments when supplied. include_next_link: Whether to wrap the result as {items, next_link} so paging can continue (default false, which returns a bare list).

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

Input Schema

NameRequiredDescriptionDefault
topNo
skipNo
next_linkNo
room_listNo
include_next_linkNo

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 at all, the description carries the full behavioral burden, and it does substantial work: it discloses the auth requirement, the Graph-side cap of 50 items per call, default page size, the rule that next_link overrides the paging arguments, and the two possible return shapes. It stops short of covering error behavior or throttling, which keeps it below a 5.

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 one-line purpose, then the permission prerequisite, then the follow-on routing, then a scannable per-argument block. Every sentence adds something an agent needs; there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description compensates by explaining that include_next_link toggles between a bare list and an {items, next_link} envelope, plus how to page. Combined with the stated permission scope and per-parameter docs, an agent has everything needed to call this correctly.

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%, so the description must supply all parameter meaning — and it does for all five, including defaults, the empty-string sentinel for room_list, the paging relationship between skip and top, and the override precedence of next_link. The Args block effectively supplies the semantics the schema lacks.

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 ('List bookable meeting rooms') plus the scope ('in the tenant'). It also names the two consuming tools (graph_get_schedule for availability, graph_create_event for booking), so an agent understands what this tool produces and what it feeds, despite the crowded graph_list_* sibling set.

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?

Explicitly states the required delegated permission (Place.Read.All) and gives concrete downstream usage: take the returned email addresses to graph_get_schedule or graph_create_event. It lacks an explicit 'when not to use' or a statement about alternatives for enumerating rooms, but for a foundational list tool the guidance is clear.

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