getAccommodationsGet all accommodation types (rooms, beds) for a specific coliving. Returns pricing, capacity, and unit details.
| Name | Required | Description | Default |
|---|---|---|---|
| colivingId | Yes | The coliving ID |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It states that it returns pricing, capacity, and unit details, but does not explicitly confirm that it is a read-only operation or disclose any potential side effects. This is adequate but not exceptional.
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 a single sentence with 15 words, front-loading the key action and resource. Every word earns its place with no unnecessary filler.
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 tool with one parameter and no output schema, the description covers the main aspects: what it retrieves (accommodation types), for which entity (specific coliving), and what fields are returned (pricing, capacity, unit details). It could be improved by noting that it returns a list or array, but overall it is sufficient.
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% with a minimal description for colivingId. The description adds context that it is for a 'specific coliving' but does not provide additional meaning beyond the schema, such as data type or format constraints.
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 clearly specifies the verb 'Get' and the resource 'all accommodation types for a specific coliving', and distinguishes itself from siblings like checkAvailability and getColivingById by focusing on accommodation types with pricing and capacity.
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 implies usage by requiring a colivingId, but does not explicitly state when to use this tool over alternatives or provide any exclusion criteria, such as when checkAvailability might be more appropriate.
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.
Each tool has a clearly distinct purpose: search by different criteria, get details, check availability, list categories. The only potential overlap (checkAvailability vs checkAvailabilityBySlug) is differentiated by input type (ID vs slug), which is a reasonable distinction.
All tools follow a consistent camelCase pattern with lowercased verbs followed by nouns (e.g., checkAvailability, getColivingsByBudget). No mixing of conventions (e.g., snake_case, PascalCase) is present.
With 14 tools, the server covers the core operations for a coliving discovery platform: searching by multiple filters, viewing details, checking availability, and accessing metadata. The count feels well-scoped without being overwhelming or sparse.
The tool surface covers the main user journeys: discovering colivings via various criteria, getting detailed information, checking availability, and reading reviews. Minor gaps include the lack of combined filtering (e.g., country + budget) and no booking tool, but these are likely outside the intended read-only scope.