Return the verified booking action (ReserveAction target URL + phone) for a business so you can hand your user off to complete a booking. v1 is a booking handoff; payment settlement is a gated roadmap capability.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations include readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false. The description adds context about returning a handoff URL and the v1 limitation (payment settlement gated), which is useful. However, it does not clarify whether the tool itself has side effects (e.g., does it reserve anything?), and readOnlyHint=false suggests it might. No explicit contradiction, but the description could be more transparent about potential mutations.
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 description is two concise sentences, with the core purpose front-loaded and the version context as a secondary note. Every word earns its place; no fluff or redundancy.
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 one-parameter tool with no output schema, the description should at least clarify the parameter's meaning and expected return structure. It states the return type (ReserveAction URL + phone) but not the format or any error conditions. The missing parameter explanation is a significant gap, making the tool only partially usable without additional context.
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 0%, so the description must compensate. It mentions 'for a business' but never explicitly maps the 'id' parameter to a business identifier. The agent is left to infer that id refers to a business, which is a gap given the sibling tools likely take similar IDs.
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 states a clear action: returns the verified booking action (ReserveAction target URL + phone) for a business. It explicitly differentiates from siblings (discover_businesses, get_business) by focusing on booking handoff, and adds version context. The verb+resource is specific and unambiguous.
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?
The description implies when to use it: when the user wants to complete a booking, by handing off to the booking action. It does not explicitly contrast with alternatives, but the sibling names (discover/get) make the purpose clear. It lacks explicit exclusions but the context is adequate.
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.
Each tool serves a distinct function: searching for businesses, getting a single business's full profile, and performing a booking handoff. There is no overlap or ambiguity in their purposes.
Tool names are all imperative verbs ('book', 'discover_businesses', 'get_business'). Two follow the verb_noun pattern, while 'book' is a standalone verb, but the style is consistent and clear.
With 3 tools, the set is compact but well-scoped for a booking gateway. It provides the essential actions (discover, retrieve, book) without redundancy, though it is on the minimal side.
The tools cover the full user journey: searching for businesses, examining details, and initiating a booking. There are no obvious dead ends, and the scope is clearly defined by the booking gateway purpose.