getColivingsByCountrySearch for coliving spaces in a specific country. Use ISO 3166-1 alpha-2 country codes (e.g., 'pt' for Portugal, 'es' for Spain, 'th' for Thailand).
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of results to return | |
| countryCode | Yes | ISO 3166-1 alpha-2 country code (e.g., 'pt', 'es', 'th') |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. Does not mention pagination, result format, or behavior when no results found. Only states input format.
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?
Two sentences, front-loaded, no extraneous words. Efficient and clear.
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?
Adequate for a simple search tool but missing behavioral details like list return and limit parameter usage. Could be more complete.
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 covers 100% of parameters with descriptions. Description adds example country codes but adds minimal value 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 'Search for coliving spaces in a specific country' with specific verb and resource, and differentiates from siblings like getColivingsByContinent and getColivingsByBudget by focusing on country-level search.
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 format for country code but no explicit when-to-use or when-not-to-use guidance. Agents must infer from tool name and sibling context.
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.