plumbing-booking

Request a Booking (sends SMS confirmation code)

request_booking

Destructive

Use this only after the user explicitly asks to start a Johnson Bros. booking and confirms their own contact details, service address, issue, and preferred windows. It sends a six-digit SMS code and does not schedule a visit. Do not claim an appointment exists until confirm_booking returns status:confirmed and booked:true.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes	Customer full name
`email`	No
`notes`	No	Issue description / anything the technician should know
`phone`	Yes	Customer mobile number — receives the 6-digit confirmation code
`address`	Yes
`service`	Yes	Requested service, e.g. "water heater replacement"
`confirmed`	Yes	True only after the user explicitly asks to start this booking request and send the SMS code
`customer_type`	No	Required for booking: answer to Have you used us before?
`referral_code`	No
`heard_about_us`	No	Required for new customers: where they found us
`time_preference`	No	Fallback time-of-day preference if none of the preferred windows is open	any
`preferred_windows`	No	Preferred arrival windows from get_availability (start_time/end_time ISO strings)
`promotion_review_requested`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`error`	No
`status`	Yes
`success`	Yes
`next_step`	Yes
`booking_id`	No
`error_code`	No
`expires_at`	No
`code_sent_to`	No
`review_sandbox`	No
`in_service_area`	No
`attempts_allowed`	No
`service_area_notice`	No
`sandbox_verification_code`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 13, 2026

addedInput schema / properties / customer_type

Added value: +{
+  "description": "Required for booking: answer to Have you used us before?",
+  "enum": [
+    "new",
+    "returning"
+  ],
+  "type": "string"
+}

addedInput schema / properties / heard_about_us

Added value: +{
+  "description": "Required for new customers: where they found us",
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}

Changed1 schema field changedSep 4, 2026
- addedInput schema / properties / referral_code
```
Added value: +{
+  "maxLength": 300,
+  "type": "string"
+}
```
First observedAug 22, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already flag openWorld, non-idempotent, destructive, but the description adds substantive behavior the annotations cannot convey: an SMS code is sent, no visit is scheduled, and the booking is not real until confirm_booking confirms. It omits one meaningful trait implied by idempotentHint=false — that repeated calls send additional codes — so it falls just short of full disclosure.

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?

Three sentences, each earning its place: precondition, effect, postcondition. The most decision-relevant facts (SMS-only, not an appointment) are front-loaded rather than buried.

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?

An output schema exists so return values need not be explained, and the description covers the gating and post-condition that matter most for a side-effecting tool. It stops short of covering conditional parameter requirements (customer_type/heard_about_us) and error/failure paths, which is a modest gap for a 13-parameter mutation.

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 69% across 13 parameters (5 required, 2 enums, nested address), so the schema carries most parameter documentation. The description adds only a workflow-level hint ('confirms their own contact details, service address, issue, and preferred windows') and says nothing about customer_type, heard_about_us, referral_code, or promotion_review_requested.

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?

States a specific verb+resource (request a booking) and immediately clarifies the actual effect: it sends a six-digit SMS code and does not schedule a visit. This distinguishes it from siblings like confirm_booking and get_availability without needing to open either schema.

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 gating ('only after the user explicitly asks to start a Johnson Bros. booking and confirms their own contact details, service address, issue, and preferred windows') plus an explicit when-not: do not claim an appointment exists until confirm_booking returns status:confirmed and booked:true. The alternative tool and its success condition are both named.

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

All plumbing-booking tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?