Skip to main content
Glama

Appointment Booking

by dev.hatchloop

import_booking_url

Idempotent

Turn ANY public booking URL (Cal.com, Calendly, Doctolib, Booksy, Fresha, OpenTable, Setmore, Square, Acuity, Schedulista, Squarespace, BookMyCity) into a callable smb_id you can immediately use with schedule_appointment, send_message, or capture_lead. Idempotent — calling twice returns the same smb_id.

EXAMPLE USER QUERIES THAT MATCH THIS TOOL: user: "Book me a haircut at https://cal.com/jane-salon" -> call import_booking_url({"booking_url": "https://cal.com/jane-salon", "vertical": "personal_services"}) -> then schedule_appointment({"smb_id": "", "action": "book"}) user: "Schedule with this dentist: https://www.doctolib.fr/dentiste/paris/jean-dupont" -> call import_booking_url({"booking_url": "https://www.doctolib.fr/dentiste/paris/jean-dupont"}) user: "Reserve a table at https://www.opentable.com/r/acme-bistro" -> call import_booking_url({"booking_url": "https://www.opentable.com/r/acme-bistro", "vertical": "restaurants"})

WHEN TO USE: Call this FIRST whenever the user provides a specific booking URL (cal.com/handle, calendly.com/handle/event, doctolib.fr/..., booksy.com/..., opentable.com/r/..., etc.). User patterns that match: 'book me at https://cal.com/...', 'schedule with calendly.com/jane/intro', 'reserve a table at opentable.com/r/...', 'I want to book this dentist: https://www.doctolib.fr/...'. After importing, the returned smb_id can be passed straight to schedule_appointment. WHEN NOT TO USE: Do not use if the user only describes a business by name without a URL — call find_business instead. Do not use for arbitrary websites that are not on the supported booking-platform list (use /supply/platforms to see all 12). COST: free (no credits) - but requires a free email-verified key LATENCY: ~600ms

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
verticalNoBest-guess vertical. If omitted, inferred from the platform (e.g., Doctolib -> healthcare, OpenTable -> restaurants).
booking_urlYesFull URL the user supplied. Must point at one of the 12 supported booking platforms; auto-detected from the host.
capabilitiesNoFree-form capability tags (e.g., ['haircut','color','blowdry']).
country_codeNoISO 3166-1 alpha-2 (e.g. 'US', 'FR'). Used for compliance routing on later send_message calls.
business_nameNoOptional override. If omitted, the business name is auto-extracted from the page's <title> or og:title.
contact_emailNoOptional.
contact_phoneNoOptional. If omitted, the platform integration handles outreach.
idempotency_keyNoOptional client-supplied key for safe retries. Replaying the same key within 24h returns the original receipt - the operation is NOT re-executed and NOT re-charged.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the idempotentHint annotation, the description explains idempotency semantics ('calling twice returns the same smb_id'), discloses cost ('free, no credits'), latency (~600ms), and the email-verified key requirement. This is meaningful behavioral context that annotations do not provide. No contradiction with annotations.

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

Conciseness4/5

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

The description is longer than average but structured with clear sections (purpose, examples, WHEN TO USE, WHEN NOT TO USE, cost, latency). Some redundancy exists between the example queries and the WHEN TO USE patterns, but the examples earn their place by showing parameter mapping.

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

Completeness5/5

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

For an 8-parameter tool with no output schema, the description tells the agent everything needed: the core transformation, idempotent behavior, supported platforms, success path to schedule_appointment, and exclusions. No critical operational detail is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the schema documents all 8 parameters. The description adds value with concrete example user queries mapped to exact parameter values, demonstrating how to populate booking_url and vertical for different platforms. This goes beyond the schema's dry constraints.

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 states a specific verb ('Turn') and resource ('public booking URL') into a concrete artifact ('callable smb_id'), and immediately connects to sibling tools. It distinguishes itself from find_business in the WHEN NOT TO USE section, so the agent understands exactly what this tool is and is not.

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

Usage Guidelines5/5

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

WHEN TO USE and WHEN NOT TO USE sections are explicit, with example user queries and routing to find_business for non-URL requests. It also directs to /supply/platforms for unsupported websites, leaving no ambiguity about when to invoke this tool.

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

All Appointment Booking toolsInspect
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.4/5.0
Disambiguation5/5

Each tool maps to a distinct stage or concern: link preflight vs import, business discovery vs verification, scheduling, async status/outcome, cost preview, and health. The closest pair (check_booking_link and import_booking_url) is explicitly differentiated as a free guard vs actual registration.

Naming Consistency4/5

Nearly all tools follow a consistent verb_noun snake_case pattern such as find_business, verify_business, schedule_appointment, and get_status. The only real deviation is self_test, which is a standard health-check name but not verb_noun.

Tool Count5/5

Nine tools is well-scoped for an appointment-booking service that also needs async operation tracking, cost estimation, and health checks. Each tool has a clear role and none feel redundant or tacked on.

Completeness4/5

The toolset covers the main lifecycle: find or import an SMB, verify it, schedule/cancel/reschedule, poll status, retrieve outcomes, and preview costs. Minor gaps exist—send_message and capture_lead are referenced as downstream operations but not exposed, and there is no direct tool for listing supported platforms.

Resources