agentorist

request_unsupported_booking

Destructive

Log a booking request Agentorist can't yet fulfil.

This is the demand-intelligence engine. Every call here becomes a data point sold to the venue as monthly missed-revenue insight. Optionally captures email so the user is notified when the venue joins.

Input Schema

TableJSON Schema

Name	Required	Description
`location`	No	City or area.
`vertical`	Yes	Which vertical the request belongs to.
`when_iso`	No	Requested time in ISO 8601 (optional).
`item_title`	Yes	The film, event, or experience.
`party_size`	No	Number of tickets.
`user_email`	No	Optional, for join-notification.
`venue_name`	Yes	Name of the venue the user wanted.
`venue_chain`	No	e.g. Vue, Odeon, Cineworld.
`agent_client`	No	Calling agent (Claude, ChatGPT, etc.).

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A3.9/5.0

Behavior4/5

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

Description adds context beyond annotations by explaining that calls become data points sold to venues and optionally notifies the user via email. Aligns with 'destructiveHint: true' as a record-creation operation.

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?

Description is four sentences, front-loaded with purpose, no wasted words. Efficiently conveys core functionality and business value.

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

Completeness3/5

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

Despite output schema existing, the description lacks guidance on when to use this tool versus siblings (e.g., 'book', 'search'), prerequisites, or error handling. Adequate for basic understanding but incomplete for optimal selection.

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 has 100% description coverage, so baseline is 3. Description adds minimal parameter-specific meaning, only highlighting 'user_email' for join-notification. Most parameters are explained adequately in schema.

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?

Description uses specific verb 'Log' and resource 'booking request' that aligns with tool name. Differentiates from sibling 'book' by indicating this is for unsupported bookings.

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?

Implicitly suggests use when a booking can't be fulfilled by Agentorist, but does not explicitly state when not to use or mention alternatives like 'search' to check venue support. Lacks direct usage guidance.

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?