GET /rooms — List your subscribed rooms
Returns every room you are subscribed to (DMs, group DMs, channels you follow, discussions, activities, event rooms), sorted by lastActivityAt descending. Cursor-paginated.
To filter by type use GET /rooms/inbox/:type (e.g. /rooms/inbox/dm for DMs only).
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results (1-100) | |
| cursor | No | Cursor from a previous response's `nextCursor`. Pass to fetch the next page. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations present, so description carries full burden. It discloses cursor-paginated behavior and sorting order. Could mention that it's read-only, but the GET verb implies it. Lacks details on side effects or response structure beyond pagination.
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 sentences, front-loaded with endpoint and purpose. No wasted words; each sentence adds essential information.
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?
Given no output schema, description explains return types (list of rooms) and sorting. Lacks details on response shape (room object fields) but sufficient for a list tool.
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 100%, so baseline is 3. Description adds value by explaining cursor usage ('from a previous response's nextCursor') and reinforces limit default. Confirms pagination context beyond schema.
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?
Description clearly states the tool lists subscribed rooms with specific types (DMs, group DMs, channels, etc.) and mentions sorting by lastActivityAt. It distinguishes itself from sibling tools like rooms_inbox or rooms_browse.
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?
Provides explicit when-to-use (list all rooms) and when-not-to-use via alternative: 'To filter by type use GET /rooms/inbox/:type'. This helps the agent choose correctly.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Despite the large number of tools, each has a detailed description that clearly distinguishes its purpose. Minor potential overlaps (e.g., search vs. resource-specific search, own vs. other's agenda) are well documented, so an agent can differentiate them.
Tool names follow a consistent verb_noun or resource_subresource_action pattern in snake_case. A few tools are just nouns (e.g., 'alerts', 'announcements'), but these are top-level listing endpoints; overall the naming is predictable.
85 tools is very high for a single server, making it difficult for an agent to efficiently explore and select the right tool. While each tool seems justified for the broad domain, the count feels overwhelming and could be streamlined.
The tool surface covers most major areas (events, trips, chapters, rooms, search, profile, etc.) with CRUD or lifecycle operations. However, the lack of a 'send message' tool for rooms is a notable gap, and some resources (e.g., events) are read-only on creation/update, limiting agent workflows.
