agentorist

search

Read-only

Search for bookable items within a vertical.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`when`	No	Optional ISO date filter (YYYY-MM-DD) for events.
`query`	Yes	Natural-language query — movie title, event keyword, tour name, theme like "beach getaway", etc.
`rooms`	No
`adults`	No
`locale`	No	Optional BCP-47 locale ('en-US', 'fr-FR', 'de-DE', 'ja-JP', etc.). Currently consumed by the 'experiences' vertical to localise the Viator response and hand-off URL. Auto-detected from the query when the language is unambiguous.
`check_in`	No
`children`	No
`location`	Yes	City, postcode, or "lat,lng".
`vertical`	Yes	One of the names returned by list_verticals (e.g. "movies", "events", "experiences", "hotels", "cars").
`check_out`	No
`territory`	No	ISO country code (US, GB, etc.). Default US.	US
`driver_age`	No
`hotel_name`	No
`hotel_class`	No
`pickup_date`	No
`agent_client`	No	Optional — name of the calling agent (Claude, ChatGPT, etc.).
`budget_range`	No
`dropoff_date`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A3.7/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, so the tool is read-only. The description adds no further behavioral context beyond the basic search function, which is adequate but not enhanced.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single clear sentence with no wasted words, front-loaded with the essential action and resource.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of 18 parameters, low schema coverage, and the presence of sibling tools, the description is too minimal. It does not explain how the required 'vertical' relates to list_verticals or how this tool fits into the booking workflow.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is low (39%) and the tool description adds no parameter meaning beyond what the schema provides. The description does not compensate for the missing parameter details.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description succinctly states the tool searches for bookable items within a vertical, clearly distinguishing it from sibling 'search_all' which searches across all verticals. It uses a specific verb and resource.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context ('within a vertical') implying when to use this tool versus search_all, but does not explicitly state when not to use or mention alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All agentorist tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation5/5

Each tool has a clear, distinct role: discovery (search, search_all, list_verticals, list_venues), options (find_options), booking (book), and user feedback (request_unsupported_booking). No two tools perform the same function.

Naming Consistency3/5

Some tools follow verb_noun (list_venues, list_verticals, find_options, request_unsupported_booking), while others are single verbs or verb_adverb (book, search, search_all). The inconsistency in pattern may confuse an agent.

Tool Count5/5

Seven tools is well-scoped for a booking discovery service. Each tool covers a necessary step in the user journey without being overwhelming or sparse.

Completeness4/5

The set covers the core workflow: discover verticals, search, get options, book, and flag unsupported requests. Minor gaps exist (e.g., no tool to view or cancel bookings), but these are beyond the stated purpose.

Resources

Need Help?