List confirmed or cancelled room bookings for a calendar within a window that defaults to the next seven days.
List the bookings of a calendar Confirmed bookings in a window, soonest first. The window defaults to the next seven days. TRMNL GET /api/apps/room_booking/{installation_id}/calendars/{id}/bookings.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | ||
| query | No | ||
| profile | No | Configured profile name; defaults to default. |
Changes observed during successful MCP inspections.
v0.2.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuine context beyond that: results are filtered to confirmed bookings by default, ordered soonest-first, and scoped to a default seven-day window. It stops short of describing the response shape 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short lines, front-loaded with the purpose and behavior; nothing is padded. The trailing raw endpoint string is of limited use to an agent but is compact and serves as an identifier for the underlying API route.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema and a nested 3-parameter schema, the description should say more about what a booking record contains or whether results are bounded/paginated. It covers the temporal window well but leaves the return value entirely unexplained for a list operation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 33%, and the description largely restates what the schema already documents (from defaults to now, to defaults to from+7 days, status defaults to confirmed). It says nothing about the 'profile' parameter or the path identifiers beyond echoing the raw URL template, so it does not compensate for the coverage gap.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource ('List the bookings of a calendar') and adds ordering ('soonest first') plus a default window, which distinguishes it from siblings like trmnl_list_room_booking_calendars or trmnl_get_room_booking. It never names a sibling explicitly, so the differentiation is inferred rather than stated.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The default window ('next seven days') and default status ('Confirmed bookings') imply typical usage, but there is no explicit when-to-use guidance, no exclusions, and no pointer to alternatives such as trmnl_list_room_booking_calendars or trmnl_get_room_booking_calendar.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.