getAllCountriesGet a list of all countries that have active colivings on Mapmelon, grouped by continent. Shows the number of colivings in each country.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It describes the output (grouped by continent, count) but does not disclose potential limitations like data freshness or pagination. Adequate for a simple read tool.
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, no wasted words, clearly states what the tool does and what the output contains.
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 parameterless tool with no output schema, the description fully covers what the tool returns (list of countries with colivings, grouped by continent, with count). No gaps.
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?
No parameters present, baseline score 4 per guidelines. Description adds no parameter information, which is acceptable since none exist.
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 uses specific verb 'get list' and resource 'countries with active colivings', clearly distinguishing from siblings like getColivingsByCountry (filter by country) and getColivingsByContinent (filter by continent).
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?
No explicit when-to-use or when-not-to-use guidance. The purpose implies use for overview, but lacks explicit alternatives or exclusions.
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.