Fetches category-organized amenity list for a Point of Interest.
| Name | Required | Description | Default |
|---|---|---|---|
| lang | No | Optional language code (e.g. 'en_US'). | |
| currency | No | Optional currency code (e.g. 'USD'). | |
| contentId | Yes | The unique ID of the POI. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the disclosure burden. It communicates that results are organized by category and that the operation is a read-only fetch, but it does not address potential limitations, response shape details, or any edge-case behavior.
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, front-loaded sentence with no filler. Every word contributes to understanding the tool's purpose and output organization.
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 fetch tool with fully documented schema parameters, the description supplies the core purpose and output nature. An output schema is absent, but 'category-organized amenity list' provides adequate expectation setting, though usage guidance is missing.
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 description coverage is 100%, so the baseline is 3. The description adds no parameter-specific meaning beyond what the schema already documents for contentId, lang, and currency.
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 uses specific verb 'Fetches' and resource 'category-organized amenity list for a Point of Interest', clearly differentiating it from sibling tools like get_details and get_poi_reviews. The scope is unambiguous.
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 use when amenity information for a POI is needed, but it does not explicitly state when to prefer this over sibling tools or mention any exclusions. No alternatives are named.
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.
While most tools have clear specific purposes, 'get_details' overlaps with 'get_poi_full_about' and could be confused with the more specific getters like 'get_poi_amenities' or 'get_poi_reviews'. The distinction between a generic details endpoint and a detailed metadata profile is not immediately obvious.
The naming convention is mixed: most tools use a 'get_' prefix (get_details, get_media_gallery, get_poi_*), but 'search_listings', 'typeahead', and 'usage_statistic' break that pattern. The verbs are also inconsistent (get vs search vs typeahead), making the set feel less predictable.
With 8 tools, the server is well-scoped for a travel and POI information service. Each tool serves a distinct purpose in the overall workflow of searching, retrieving details, and viewing ancillary data like media, amenities, and reviews. No tools feel redundant or excessive.
The toolset covers the core needs for exploring Points of Interest: search/typeahead, detailed information, media, amenities, reviews, and API usage stats. A minor gap is the lack of a direct 'get_poi_by_id' function, but 'get_details' likely covers that. The available tools form a coherent workflow without major dead ends.