agentorist

find_options

Read-only

Find concrete bookable options for an item.

For movies: showtimes for the given film. For events: ticket classes.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`when`	No	ISO date (YYYY-MM-DD) or "today"/"tomorrow". Default "today".	today
`item_id`	Yes	ID returned by `search` (film_id, event_id), or a title for fuzzy lookup.
`location`	No	City, postcode, or "lat,lng" — required for movies.
`vertical`	Yes	The vertical (e.g. "movies", "events").
`agent_client`	No	Optional — name of the calling agent (Claude, ChatGPT, etc.). Pass the SAME value across search → find_options → book so the trust stack can link the booking to its prior discovery.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description is consistent. It adds value by specifying the output type for different verticals (showtimes vs. ticket classes), which is beyond what annotations provide.

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 extremely concise: two sentences that immediately state the core purpose and provide vertical-specific examples. Every word is necessary, and it is front-loaded with the main action.

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

Completeness4/5

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

Given the output schema exists, the description does not need to detail return values. It covers the main use cases (movies, events) and mentions key parameters. However, it does not explain the 'when' or 'agent_client' parameters, though the schema covers them.

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

Parameters3/5

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

Schema coverage is 100%, so the baseline is 3. The description does not add additional meaning beyond the schema; it merely repeats the vertical-specific behavior. No parameter details are elaborated.

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 clearly states the tool's purpose: 'Find concrete bookable options for an item.' It distinguishes itself from siblings by specifying it returns showtimes for movies and ticket classes for events, which differentiates it from search or booking tools.

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

Usage Guidelines3/5

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

The description provides context by mentioning movies and events, but it lacks explicit guidance on when to use this tool versus alternatives like search or list_venues. No exclusions or when-not-to-use information is provided.

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?