plumbing-booking

Get Open Booking Windows

get_availability

Read-onlyIdempotent

Use this when the user wants live Johnson Bros. appointment availability. Include zip and any known town/state for a customer booking inquiry. Outside-area or unresolved locations receive no windows. Without a location, this returns general capacity only, not eligibility to book; coverage_status is not_checked. Never call for a customer already found outside coverage. Do not promise or create an appointment; use request_booking and confirm_booking.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_availability"
  }
}

Input Schema

Name	Required	Description	Default
`zip`	No	Service ZIP when known. Always include the customer location for a booking inquiry; outside-area requests receive no windows.
`days`	No	How many calendar days to search from start_date (or today), 1 to 14; default 7.
`town`	No	Service town when known, e.g. "Quincy", sent alongside zip. A town without a ZIP returns needs_more_information; use check_service_area for town-only coverage questions.
`state`	No	Two-letter state code, normally MA; send only together with zip or town.
`start_date`	No	First day to search as YYYY-MM-DD in the company time zone; omit for today. Past dates are rejected.
`time_preference`	No	Part of day to keep: any (default), morning, afternoon or evening.	any

Output Schema

Name	Required	Description	Default
`status`	No
`privacy`	Yes
`success`	Yes
`windows`	Yes
`has_more`	No
`timezone`	Yes
`next_step`	No
`error_code`	No
`booking_flow`	Yes
`open_windows`	Yes
`total_windows`	Yes
`missing_fields`	No
`requested_days`	Yes
`review_sandbox`	No
`coverage_status`	No
`time_preference`	Yes
`returned_windows`	No
`total_matching_windows`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 21, 2026

addedInput schema / properties / days / description

Added value: +"How many calendar days to search from start_date (or today), 1 to 14; default 7."

addedInput schema / properties / start_date / description

Added value: +"First day to search as YYYY-MM-DD in the company time zone; omit for today. Past dates are rejected."

addedInput schema / properties / state / description

Added value: +"Two-letter state code, normally MA; send only together with zip or town."

addedInput schema / properties / time_preference / description

Added value: +"Part of day to keep: any (default), morning, afternoon or evening."

addedInput schema / properties / town / description

Added value: +"Service town when known, e.g. \"Quincy\", sent alongside zip. A town without a ZIP returns needs_more_information; use check_service_area for town-only coverage questions."

Changed8 schema fields changedSep 14, 2026

addedInput schema / properties / state

Added value: +{
+  "maxLength": 2,
+  "minLength": 2,
+  "type": "string"
+}

addedInput schema / properties / town

Added value: +{
+  "maxLength": 60,
+  "minLength": 2,
+  "type": "string"
+}

addedInput schema / properties / zip

Added value: +{
+  "description": "Service ZIP when known. Always include the customer location for a booking inquiry; outside-area requests receive no windows.",
+  "maxLength": 10,
+  "minLength": 3,
+  "type": "string"
+}

addedOutput schema / properties / coverage_status

Added value: +{
+  "enum": [
+    "verified",
+    "not_checked",
+    "outside_service_area",
+    "unknown"
+  ],
+  "type": "string"
+}

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

addedOutput schema / properties / missing_fields

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

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

addedOutput schema / properties / status

Added value: +{
+  "enum": [
+    "available",
+    "needs_more_information",
+    "outside_service_area",
+    "unavailable"
+  ],
+  "type": "string"
+}

Changed3 schema fields changedSep 13, 2026
- addedOutput schema / properties / has_more
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / returned_windows
```
Added value: +{
+  "type": "integer"
+}
```
- addedOutput schema / properties / total_matching_windows
```
Added value: +{
+  "type": "integer"
+}
```

Changed5 schema fields changedSep 12, 2026

addedOutput schema / properties / windows / items / properties / arrival_end

Added value: +{
+  "description": "Customer-facing two-hour arrival promise.",
+  "type": "string"
+}

addedOutput schema / properties / windows / items / properties / arrival_start
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / windows / items / properties / end_time / description

Added value: +"Reserved three-hour job-block end; pass unchanged to request_booking."

addedOutput schema / properties / windows / items / properties / start_time / description
```
Added value: +"Selected job-block start; pass unchanged to request_booking."
```

changedOutput schema / properties / windows / items / required

Previous value: -[
-  "start_time",
-  "end_time",
-  "start_local",
-  "end_local",
-  "part_of_day",
-  "available"
-]New value: +[
+  "start_time",
+  "end_time",
+  "arrival_start",
+  "arrival_end",
+  "start_local",
+  "end_local",
+  "part_of_day",
+  "available"
+]

First observedAug 22, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), but the description goes further and discloses outcome behavior not present in any structured field: outside-area or unresolved locations receive no windows, and a location-less call returns general capacity only with coverage_status not_checked. These failure-mode semantics are exactly what an agent needs to avoid misreporting availability as bookability.

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 trigger condition, then constraints, then exclusions; every clause carries real routing or behavior information and none is filler. It is dense to the point of being slightly clipped (three constraint sentences stacked without connective tissue), which keeps it just below 5.

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?

An output schema exists, so return-value documentation is unnecessary; the description instead supplies the coverage/eligibility caveats and the routing to sibling tools that the schema cannot express. For a 6-parameter, zero-required lookup tool with a rich schema, nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3; the description earns an extra point by stating which parameters matter most for the primary use case ('Include zip and any known town/state for a customer booking inquiry') and the consequence of omitting location. It does not add format or syntax detail beyond the schema, so it stops short of 5.

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 and resource (retrieve live Johnson Bros. appointment availability) and immediately distinguishes itself from the write-path siblings by warning not to create or promise appointments and pointing to request_booking/confirm_booking. An agent can tell this apart from check_service_area and the booking tools without opening any 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?

Gives explicit when-to-use (customer booking inquiry with a location), when-not (never for a customer already found outside coverage), and named alternatives (request_booking, confirm_booking, plus check_service_area for town-only questions in the schema). No condition is left to inference.

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?