Skip to main content
Glama

Book an appointment

request_booking
Destructive

Use this when the user wants to book a local home-service appointment and has already chosen an open time. Confirms the appointment when the slot is open. An on-site offering returns status confirmed, visit_type on_site, scheduled_start, and address, and the message names a confirmed on-site technician visit at that address and time. A phone offering names a confirmed phone call. Do not describe a confirmed on-site visit as a call, a consult, or unverified. Calling this again with the same details can create a second booking; if unsure, check get_booking_status first. Requires consent: before calling, show the user the consent text in the consent field and get their agreement. Also requires a name, a valid email, and a problem description. service_address is optional for a phone consult and required for an on-site visit. Disposable, reserved, and blocked email domains are rejected. job_summary falls back to problem. service_area is inferred from the address or city, otherwise the shop city. A phone consult accepts a street, a city and ZIP, or a PO Box. An on-site visit needs a street address. Shop-specific booking rules and emergency_phone come from get_business. offering is an id from get_business. start is an ISO-8601 timestamp, for example 2026-10-20T14:00:00-04:00. The start is at least 2 hours ahead and no more than 21 days ahead. A start outside that window names the field start. Returns status confirmed, a cancel link, and verify_url when the signed receipt is ready. The receipt page does not show the customer. An optional idempotency_key repeats the same result for that shop. The result offers an unchecked choice, "save my details and get updates from Booqer". Leave updates_opt_in unset. Set it true only after the user agrees to that exact sentence. It does not change the booking. Rate limited per IP and per shop, with a per-shop daily cap.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "shop_id": "<shop_id>",
      "offering": "<offering>",
      "name": "<name>",
      "email": "<email>",
      "start": "<start>",
      "consent": "<consent>",
      "problem": "<problem>"
    },
    "name": "request_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesCustomer name. Example: Ada Lovelace.
emailYesCustomer email on a real domain. Example: ada@gmail.com. Disposable and example.com addresses are rejected.
phoneNoCustomer phone. Example: 3525550100. Optional.
startYesISO-8601 timestamp with an offset. Example: 2026-10-20T14:00:00-04:00. At least 2 hours ahead and no more than 21 days ahead.
consentYesRequired. Before you call this tool, show the user this exact text and get their agreement: "I agree to Booqer's Terms and Privacy Policy and consent to Booqer sharing my request with this shop so they can contact me about it." Terms: https://booqer.ai/terms. Privacy Policy: https://booqer.ai/privacy. Set true only after the user agrees. Without consent true the call is rejected and nothing is stored.
problemYesWhat is wrong, in the customer's words. Example: Gate will not close.
shop_idYesEnrolled shop id from search_businesses. Examples: florida-pole-barn, florida-security-concepts, booqer-demo-shop.
offeringYesService id from get_business. Example: project_consult.
job_summaryNoShort job summary. Falls back to problem when omitted.
service_areaNoCity or county. Inferred from the address when omitted. Example: Clermont.
updates_opt_inNoOmit or false. The confirmation offers "save my details and get updates from Booqer" unchecked. Set true only after the user agrees to that exact sentence.
idempotency_keyNoOptional key of 8 to 80 letters, numbers, dots, underscores, colons, or hyphens. A repeat with the same key and shop returns the first booking instead of creating another.
service_addressNoStreet, city and ZIP, or PO Box. Optional for a phone consult. Required for an on-site visit. Example: 100 Demo Drive, Clermont FL 34711.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / updates_opt_in
      Added value: +{
      +  "description": "Omit or false. The confirmation offers \"save my details and get updates from Booqer\" unchecked. Set true only after the user agrees to that exact sentence.",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, destructiveHint=true, openWorldHint=true; the description goes far beyond that with idempotency_key semantics, rate limiting per IP/shop plus a daily cap, rejection of disposable/reserved/blocked email domains, the 2-hour-to-21-day start window, the fact the receipt page does not show the customer, and that updates_opt_in does not change the booking. All of this is behavior an agent could not infer from the 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?

Front-loaded with the selection criterion and safety warnings, and nearly every sentence carries operational weight. The only waste is a block of parameter prose that restates schema descriptions, and the whole thing is a single dense paragraph without structure for 13 parameters.

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 a destructive, open-world, 13-parameter mutation, the description covers consent mechanics, duplicate-booking risk, validation rules, time windows, rate limits, and the opt-in trap. The output schema is present and the description's return-value summary is a bonus rather than a crutch.

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 schema already documents every parameter, and much of the description's parameter text (job_summary fallback, service_address conditional requirement, start window, offering source) duplicates the schema verbatim. It does add a little beyond the schema, notably that service_area falls back to the shop city and that a phone consult accepts a PO Box, but that is a marginal increment over an already-complete 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?

Names a specific verb and resource ('book a local home-service appointment') and scopes it to a precondition ('has already chosen an open time'), which cleanly separates it from check_availability and get_booking_status without naming them. The agent can tell immediately what this tool does and what state the conversation must be in.

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?

Explicit when-to-use ('already chosen an open time'), explicit warnings ('calling this again with the same details can create a second booking'), and an explicit fallback ('if unsure, check get_booking_status first'). It also states prerequisites (consent, name, email, problem) and conditional parameter requirements (service_address optional for phone, required for on-site).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources