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.

Input Schema

TableJSON 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
`town`	No
`state`	No
`start_date`	No
`time_preference`	No		any

Output Schema

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

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

Behavior5/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is known. The description adds crucial behavioral context beyond annotations: 'Outside-area or unresolved locations receive no windows' and 'Without a location, this returns general capacity only, not eligibility to book; coverage_status is not_checked.' These edge-case behaviors are essential for correct use and are not covered by annotations. No contradiction exists.

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 six sentences long but every sentence carries operational weight—purpose, required inputs, edge-case behavior, exclusions, and sibling routing. It is front-loaded with the purpose and ends with clear guardrails. There is no fluff or redundancy, so it earns a top score for conciseness despite its length.

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?

Given that an output schema exists (so return format is specified elsewhere), the description covers the essential operational context: when to call, what inputs to provide, what happens in edge cases, and which sibling tools to use instead. It is complete enough for an agent to invoke this tool correctly without further documentation.

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 only 17% (only zip has a description). The description compensates partially by instructing 'Include zip and any known town/state for a customer booking inquiry,' which clarifies the role of location parameters. However, it gives no information about days, start_date, or time_preference, leaving the agent to infer their meaning from names and schema constraints. This is a moderate gap given the low coverage.

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 opens with a clear, specific directive: 'Use this when the user wants live Johnson Bros. appointment availability.' This names the exact resource and action, and immediately distinguishes itself from siblings by explicitly stating 'Do not promise or create an appointment; use request_booking and confirm_booking.' The verb 'get' and resource 'availability' are unambiguous, and the sibling differentiation is explicit.

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 gives explicit when-to-use and when-not-to-use guidance. It says to call this for booking inquiries and to include zip and town/state, and it warns 'Never call for a customer already found outside coverage.' It also directs the agent away from creating appointments by naming the correct sibling tools. This is exemplary routing 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?