getAllCategoriesGet all available amenity and lifestyle categories that can be used to filter colivings. Categories are grouped into: location, food, coworking, facilities, structure, activities, community.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries the burden. It indicates a read operation returning categories, but does not mention any constraints, rate limits, or data volume. The behavior is straightforward, lacking additional context.
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 two sentences, front-loaded with the main action, and contains no fluff. Every word adds value.
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?
While the tool has no parameters and is simple, there is no output schema or description of the return structure. The description lists category groups but does not specify the format (e.g., array of strings or objects), which could help an agent interpret the response.
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?
There are 0 parameters, and schema coverage is 100% (empty schema). The description adds no parameter details beyond what the schema provides, but with no parameters, a baseline of 4 is appropriate.
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 states 'Get all available amenity and lifestyle categories' with a specific verb and resource, and explains their purpose 'used to filter colivings', distinguishing it from sibling tools that filter colivings by those categories.
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 for obtaining filter options, but does not explicitly say when to use this tool over alternatives like getColivingsByAmenities or getColivingsByLifestyle. No when-not or exclusion guidance is provided.
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.