Retrieve comprehensive details, description, amenities, unedited Google star rating, guest capacity, pricing structure, and contact coordinates for a specific venue by slug or ID.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | No | The URL slug of the venue (e.g., 'shepstone-gardens') | |
| venueId | No | The unique venue ID (e.g., 'ven_shepstone_01') |
Changes observed during successful MCP inspections.
Input schema / properties / slug / descriptionPrevious value: -"The URL slug of the venue (e.g., 'the-glasshouse-muldersdrift')"New value: +"The URL slug of the venue (e.g., 'shepstone-gardens')"Input schema / properties / venueId / descriptionPrevious value: -"The unique venue ID (e.g., 'ven_1')"New value: +"The unique venue ID (e.g., 'ven_shepstone_01')"Input schema / properties / slug / descriptionPrevious value: -"The URL slug of the venue (e.g., 'the-glasshouse-muldersdrift') [Optional: omit to use server default filter]."New value: +"The URL slug of the venue (e.g., 'the-glasshouse-muldersdrift')"Input schema / properties / venueId / descriptionPrevious value: -"The unique venue ID (e.g., 'ven_1') [Optional: omit to use server default filter]."New value: +"The unique venue ID (e.g., 'ven_1')"Input schema / properties / slug / descriptionPrevious value: -"The URL slug of the venue (e.g., 'the-glasshouse-muldersdrift')"New value: +"The URL slug of the venue (e.g., 'the-glasshouse-muldersdrift') [Optional: omit to use server default filter]."Input schema / properties / venueId / descriptionPrevious value: -"The unique venue ID (e.g., 'ven_1')"New value: +"The unique venue ID (e.g., 'ven_1') [Optional: omit to use server default filter]."Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. 'Retrieve' signals a read operation and the listed fields add useful context about what is returned, but auth requirements, rate limits, and side-effect guarantees are not addressed.
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 definition is a single front-loaded sentence with no preamble or waste. The enumeration is somewhat long, but each listed field helps clarify the return content in the absence of an output schema.
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 read-only detail-fetching tool with no annotations and no output schema, the description provides strong guidance by enumerating the returned fields. It could be slightly more complete by explaining parameter selection or access requirements.
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 both slug and venueId are already documented in the schema. The description restates that the venue can be identified by slug or ID but does not clarify whether the parameters are mutually exclusive or how to choose between them.
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 a specific verb-plus-resource pattern: retrieve details for a specific venue by slug or ID. It clearly distinguishes this from search-oriented siblings like find_venues, though it does not explicitly name or contrast them.
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?
Usage is implied: this tool is for fetching a specific venue once slug or ID is known. There is no explicit guidance on when to choose this over check_venue_availability, find_venues, or request_curated_quotes, and no exclusions are stated.
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.