Lists calendar collections for a room booking installation so you can see how multiple calendars are grouped on one screen as a list or grid.
List the calendar collections A collection puts several calendars on one screen, as a list or a grid. TRMNL GET /api/apps/room_booking/{installation_id}/collections.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | ||
| 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=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds useful context about what a collection is and exposes the underlying GET endpoint, but it does not describe pagination, authorization requirements, or return 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?
The description is short and front-loaded with the primary action. The second sentence adds useful conceptual context without unnecessary detail.
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?
For a simple read-only list operation with annotations covering safety, the description is adequate. However, it omits pagination, return shape, and the purpose of the profile parameter, leaving minor gaps for an agent invoking it.
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 description coverage is only 50%, so the description should compensate. It indirectly indicates installation_id through the endpoint template, but it does not mention the profile parameter or clarify its default behavior.
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 gives a clear verb and resource: list calendar collections. It also explains what a collection is, which helps distinguish collections from individual calendars. It does not explicitly contrast with sibling tools such as list_room_booking_calendars or list_room_booking_collection_screens.
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 description does not say when to use this tool instead of alternatives, nor does it mention prerequisites or conditions. Usage is only implied by the tool name and the endpoint path.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.