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

TableJSON Schema

Name	Required	Description	Default
`name`	Yes	Customer full name, for example "Jane Smith"
`email`	No
`phone`	Yes	Customer phone number for the callback
`urgency`	No		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

TableJSON 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.

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.7/5.0

Behavior5/5

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

Annotations indicate destructiveHint=true, readOnlyHint=false, and openWorldHint=true, which already signal a write operation with side effects. The description adds valuable context by stating it 'creates a callback lead, not an appointment' and that it 'can notify the office and send a transactional SMS acknowledgment', going beyond the annotations to describe specific behavioral outcomes.

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?

The description is two sentences with no fluff. It front-loads the primary condition ('only after the user explicitly asks...') and immediately follows with the key exclusions. Every word earns its place, making it easy to parse quickly.

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 write tool with side effects, the description covers the essential usage constraints: when to use it, what it creates, what it is not, and the emergency fallback. The output schema exists (per signal), so return values are not required in the description. Nothing an agent needs to invoke it correctly is missing.

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?

The schema already provides descriptions for most parameters (name, phone, urgency, confirmed, issue_description, preferred_callback_time), giving a baseline of 3. The description references 'contact details' but does not elaborate on specific parameters or add syntax or formatting details beyond the schema. It also doesn't compensate for the email parameter which lacks a description in the 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?

The description clearly states the tool's purpose: to create a callback lead when the user explicitly requests Johnson Bros. to call them. It specifies the resource (callback lead) and distinguishes it from an appointment, and also explicitly excludes emergency dispatch, so an agent can differentiate it from siblings like request_booking or emergency_help.

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?

The description provides explicit when-to-use guidance ('only after the user explicitly asks... and provides their own contact details') and when-not-to-use guidance ('Do not use it for emergency dispatch; tell emergency users to call (617) 479-9911'). It also clarifies it is not for appointments, giving clear exclusions and alternatives.

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?