plumbing-booking

Get Plumbing Service Quote

get_quote

Read-onlyIdempotent

Use this when the user wants a non-binding estimate for a specific plumbing issue. Returns a price range, typical duration, and next step. Do not present the range as a guaranteed repair price; final pricing is confirmed on-site before work begins.

WHEN TO USE: When a customer asks "How much does it cost?", "What's the price?", or wants to know pricing before booking. Use this early in the conversation to set expectations.

PRICING NOTES:

Estimates are ranges; final price depends on on-site assessment
Do not invent urgency, after-hours, or commercial surcharges
The office or technician confirms any timing- or property-related pricing before work
The $99 service fee covers sending a technician out to diagnose the problem and give you an estimate before repair work starts. If you approve the repair, we waive the service fee and you pay only the price the technician quoted. If you decline the repair, the $99 service fee is due.

WORKFLOW:

Use this tool when customer asks about pricing
Share the estimate with appropriate caveats
If they want to proceed, use get_availability, request_booking, and confirm_booking

RETURNS: Service name, price range (min/max in USD), estimated duration, urgency notes, and suggested next steps.

Input Schema

TableJSON Schema

Name	Required	Description
`urgency`	No	How urgent is the repair?
`service_type`	Yes	Type of plumbing service (required). Examples: 'drain cleaning', 'water heater repair', 'toilet repair'
`property_type`	No	Type of property (default: 'residential')
`issue_description`	Yes	Description of the plumbing problem (required). Be specific about symptoms and location.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`error`	No
`notes`	No
`service`	No
`success`	Yes
`next_step`	No
`error_code`	No
`next_steps`	No
`description`	No
`service_fee`	No
`property_type`	No
`urgency_level`	No
`review_sandbox`	No
`service_supported`	No
`estimated_duration`	No
`estimated_price_range`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 13, 2026
- addedOutput schema / properties / error_code
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / next_step
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / service_supported
```
Added value: +{
+  "type": "boolean"
+}
```
First observedAug 22, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the remaining burden is policy disclosure, which the description carries: the estimate is non-binding, final pricing is confirmed on-site, surcharges must not be invented, and the $99 fee is waived on approval. These are substantive operational facts an agent could not infer from the schema or 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 core scope and the non-binding caveat are front-loaded, and the labeled sections make the policy and workflow easy to scan. The $99 service-fee paragraph is longer than strictly needed for tool selection, but it is genuine customer-facing policy rather than filler.

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?

With an output schema present, the description need not restate return values, and it still summarizes them. Combined with complete annotation coverage and a fully described four-parameter schema, an agent has everything needed to select and invoke this tool correctly.

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 all four parameters including the urgency and property_type enums; the description adds no format or selection guidance beyond the indirect warning against inventing urgency or commercial surcharges. This is the baseline case where the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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: a 'non-binding estimate for a specific plumbing issue', and enumerates the return contents (price range, duration, next step). It is clearly distinct from booking tools, but it never distinguishes itself from the sibling get_services_pricing, which also covers pricing, leaving that ambiguity for the agent to resolve.

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 explicit trigger conditions ('How much does it cost?', 'What's the price?'), the conversational timing ('use this early'), and a workflow that names the follow-up alternatives (get_availability, request_booking, confirm_booking). It also states a usage restriction: do not present the range as a guaranteed price.

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?