Skip to main content
Glama

Read room booking

AccountRoomBookingReadTool
Read-onlyIdempotent

A room booking installation: its summary, billing state and settings; its calendars and what each device showing one has rendered; their bookings; collections of calendars that share a screen; and the connected Google and Microsoft accounts, with the url that connects one in the browser. The installation_id comes from listAppInstallations.

  • getRoomBooking: Read a room booking installation — params: installation_id (path)

  • getRoomBookingBilling: Read the billing state of a room booking installation — params: installation_id (path)

  • getRoomBookingSettings: Read the settings of a room booking installation — params: installation_id (path)

  • listRoomBookingCalendars: List the calendars of a room booking installation — params: installation_id (path)

  • getRoomBookingCalendar: Read a calendar with its current and upcoming bookings — params: installation_id (path), id (path)

  • listRoomBookingCalendarScreens: Read the screens a calendar is showing on — params: installation_id (path), id (path)

  • listRoomBookings: List the bookings of a calendar — params: installation_id (path), id (path), from (query), to (query), status (query: one of confirmed, cancelled)

  • listRoomBookingCollections: List the calendar collections — params: installation_id (path)

  • listRoomBookingCollectionScreens: Read the screens a collection is showing on — params: installation_id (path), id (path)

  • listRoomBookingIntegrations: List the connected calendar accounts — params: installation_id (path)

  • getRoomBookingIntegrationConnectUrl: Where to send the owner to connect an account — params: installation_id (path), integration_type (path)

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": {
      "action": "<action>"
    },
    "name": "AccountRoomBookingReadTool"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesThe API operation to run
paramsNoThe operation's path, query and body parameters by name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false. The description adds useful scope details: what resources are read, the installation_id provenance, and that getRoomBookingIntegrationConnectUrl returns a browser connection URL. It does not cover permissions, errors, or pagination behavior.

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?

The description is front-loaded with a scope summary and then uses a structured operation list. Although long, every bullet earns its place by mapping an action to its parameters in a tool with eleven operations.

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?

Given eleven read operations, the description is complete enough for an agent to select an action and supply parameters. It lacks some return-format, pagination, and error detail, but annotations cover the safety profile and the tool has no output schema requiring additional explanation.

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?

The input schema only exposes a generic action enum and generic params object, so the description carries essential per-action parameter semantics. It lists path and query parameters for every operation and even specifies the status query enum values confirmed and cancelled.

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?

The description states specific read operations for a room booking installation: summary, billing, settings, calendars, screens, bookings, collections, integrations, and connect URL. It enumerates each action clearly and is distinguishable from the sibling AccountRoomBookingWriteTool by its read-only scope.

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?

The description gives clear task-level context through the action list and notes that installation_id comes from listAppInstallations. It does not explicitly state when not to use this tool or directly name the write sibling as the alternative for modifications, so it stops short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources