Loading ToolBench
Well-curated set of 6 focused tools with clear naming and typed parameters. Descriptions are contextual and explain use cases. Schema design is logical with required/optional field distinction. Minor issues: search_experiences description truncated (cut off mid-sentence), and some parameter descriptions could be more concise. The tools form a coherent domain (travel experience discovery and booking), suggesting intentional design rather than auto-generation.
Get availability information for a specific experience including dates, times, and pricing
Get detailed information about a specific experience by ID
List all category tags
Render activity tiles for a list of activity IDs, returning an embeddable widget URI
Search for travel experiences with comprehensive filtering options. Returns available categories, tags, and regions with IDs for further filtering.
Search for regions by name
search_experiences description is truncated mid-sentence (ends with 'ex: "37.7799,-122.2822". Don\'t'). This breaks understanding of the latLng parameter and tool purpose.
search_experiences input schema definition is incomplete in the provided data - the latLng property description is cut off and no other filtering options are shown in the schema, though the description mentions 'comprehensive filtering options'.
list_tags has no parameters, making its purpose less clear without seeing example responses. Why would an agent call this? When would they need to list tags before searching?
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-03-24 | C | 61 | 2025-03-26 | v1 |