marketplace

book_appointment

Idempotent

Reserve an appointment slot at a service business. Provide a unique idempotency_key to safely retry without double-booking. Get service_id from get_business and start_time/end_time from get_availability.

Input Schema

TableJSON Schema

Name	Required	Description
`notes`	No	Any special requests or notes for the business
`end_time`	Yes	ISO 8601 datetime for the appointment end (from get_availability)
`staff_id`	No	Staff member ID (from get_business). Omit to auto-assign.
`service_id`	Yes	The service ID from get_business results
`start_time`	Yes	ISO 8601 datetime for the appointment start (from get_availability)
`business_slug`	Yes	The business slug from search_businesses results
`customer_name`	Yes	Customer full name
`customer_email`	Yes	Customer email address
`customer_phone`	No	Customer phone number (optional)
`idempotency_key`	Yes	Unique key to prevent duplicate bookings (e.g. UUID). Reuse the same key to safely retry.

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already indicate idempotentHint=true and non-read-only. Description adds context of safe retry and references to prerequisite tools, aligning with and reinforcing annotations. No contradictions.

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?

Two sentences, no fluff. First sentence states purpose, second provides critical guidance. Efficient and front-loaded.

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?

For a booking tool with 10 parameters and no output schema, description covers prerequisite tools and idempotency. Could mention return value but not required. Fairly complete.

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 baseline is 3. Description adds no new parameter meaning beyond what's in schema descriptions (e.g., service_id from get_business). Adequate but not enhancing.

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?

Clearly states the verb 'Reserve' and resource 'appointment slot at a service business'. Distinguishes from siblings like cancel_appointment and reschedule_appointment.

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?

Explicitly mentions providing an idempotency key for safe retry and directs the agent to get_service_id from get_business and start_time/end_time from get_availability. Lacks explicit when-not-to-use compared to alternatives, but purpose is clear.

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

All marketplace 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

A4.1/5.0

Disambiguation5/5

Each tool targets a distinct action: booking, cancellation, availability, business details, account management, etc. Even similar tools like get_booking and list_my_bookings have clear differences in parameters and scope.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with underscores (e.g., book_appointment, get_availability, search_businesses). No mixed styles or irregular verbs.

Tool Count5/5

11 tools is well-scoped for a booking marketplace, covering customer operations, account linking, and business signup without unnecessary duplication.

Completeness4/5

The tool surface covers the core customer journey (search, view, book, cancel, reschedule) and account management. Minor gaps like business-side booking management are likely out of scope.

Resources

Need Help?