plumbing-booking

Request a Johnson Bros. Callback

request_callback

Destructive

Use this only after the user explicitly asks Johnson Bros. to call them about a plumbing need and provides their own contact details. This creates a callback lead, not an appointment, and can notify the office and send a transactional SMS acknowledgment. Do not use it for emergency dispatch; tell emergency users to call (617) 479-9911.

Input Schema

Name	Required	Description	Default
`name`	Yes	Customer full name, for example "Jane Smith"
`email`	No	Customer email, only when the customer offered it; never invent one.
`phone`	Yes	Customer phone number for the callback
`urgency`	No	How soon the customer needs the call: routine (default), soon or urgent. A callback is never emergency dispatch; life-safety situations go through emergency_help first.	routine
`confirmed`	Yes	True only after the user explicitly asks Johnson Bros. to contact them
`issue_description`	Yes	Short description of the plumbing issue
`preferred_callback_time`	No	Optional preference such as "weekday morning"

Output Schema

Name	Required	Description	Default
`status`	Yes
`message`	Yes
`success`	Yes
`next_step`	Yes
`record_id`	No
`error_code`	No
`request_id`	Yes
`phone_last4`	No
`review_sandbox`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 21, 2026

addedInput schema / properties / email / description

Added value: +"Customer email, only when the customer offered it; never invent one."

addedInput schema / properties / urgency / description

Added value: +"How soon the customer needs the call: routine (default), soon or urgent. A callback is never emergency dispatch; life-safety situations go through emergency_help first."

Changed3 schema fields changedSep 14, 2026

addedOutput schema / properties / record_id
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / request_id

Added value: +{
+  "format": "uuid",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "success",
-  "status",
-  "message",
-  "next_step"
-]New value: +[
+  "request_id",
+  "success",
+  "status",
+  "message",
+  "next_step"
+]

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 declare the write/destructive, non-idempotent, open-world profile, so the bar is lower; the description still adds real substance by disclosing the side effects (office notification, transactional SMS acknowledgment) and clarifying that a lead is not an appointment. It does not address duplicate submissions or what data is persisted, which is the only remaining gap.

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, zero filler, and the hard precondition is front-loaded before the side effects and the emergency exclusion. Each sentence carries a distinct, load-bearing instruction.

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 no explanation, and the description covers prerequisites, side effects, and the emergency escape hatch, which is sufficient for a 7-parameter lead-creation tool. The only omission is any routing cue versus the sibling request_out_of_area_callback, which matters given the open-world hint.

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 description coverage is 100%, so every parameter including the confirmed const and urgency enum is already documented in the schema itself. The description reinforces the confirmed precondition ('explicitly asks') and the ownership requirement on contact details, but adds no new syntax, format, or default semantics beyond what the schema provides. Baseline 3 applies.

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?

The description states a specific verb and resource ('creates a callback lead, not an appointment') and immediately scopes it against the appointment flow and emergency dispatch. An agent can distinguish it from request_booking and emergency_help without opening 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?

It gives an explicit precondition ('use this only after the user explicitly asks Johnson Bros. to call them and provides their own contact details') and an explicit exclusion with a redirect ('do not use it for emergency dispatch; tell emergency users to call (617) 479-9911'). This is textbook when/when-not/alternative guidance.

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?