plumbing-booking

Get Business Information

business_info

Read-onlyIdempotent

Start here for a self-contained Johnson Bros. business briefing: locations, services, hours, service area, dispatch fee, pricing and booking policies, credentials, payment methods, and how to get further information through MCP without browsing the website. Not live availability or private customer records.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`hours`	Yes
`booking`	Yes
`success`	Yes
`business`	Yes
`agent_context`	No
`facts_updated`	No
`review_sandbox`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 13, 2026

addedOutput schema / properties / agent_context / properties / availability

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "creates_appointment": {
+      "type": "boolean"
+    },
+    "kind": {
+      "type": "string"
+    },
+    "tool": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "tool",
+    "kind",
+    "creates_appointment"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / agent_context / properties / writes

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "confirm_booking": {
+      "additionalProperties": false,
+      "properties": {
+        "requires_sms_code": {
+          "type": "boolean"
+        },
+        "success_requires": {
+          "additionalProperties": false,
+          "properties": {
+            "booked": {
+              "type": "boolean"
+            },
+            "status": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "status",
+            "booked"
+          ],
+          "type": "object"
+        }
+      },
+      "required": [
+        "requires_sms_code",
+        "success_requires"
+      ],
+      "type": "object"
+    },
+    "request_booking": {
+      "additionalProperties": false,
+      "properties": {
+        "creates_appointment": {
+          "type": "boolean"
+        },
+        "requires_explicit_user_consent": {
+          "type": "boolean"
+        },
+        "sends_sms_code": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "requires_explicit_user_consent",
+        "sends_sms_code",
+        "creates_appointment"
+      ],
+      "type": "object"
+    },
+    "request_callback": {
+      "additionalProperties": false,
+      "properties": {
+        "creates_appointment": {
+          "type": "boolean"
+        },
+        "requires_explicit_user_consent": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "requires_explicit_user_consent",
+        "creates_appointment"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "request_callback",
+    "request_booking",
+    "confirm_booking"
+  ],
+  "type": "object"
+}

changedOutput schema / properties / agent_context / required

Previous value: -[
-  "instructions",
-  "timezone",
-  "locations",
-  "services",
-  "service_area",
-  "pricing",
-  "scheduling",
-  "knowledge",
-  "customer_records"
-]New value: +[
+  "instructions",
+  "timezone",
+  "locations",
+  "services",
+  "service_area",
+  "pricing",
+  "scheduling",
+  "knowledge",
+  "availability",
+  "writes",
+  "customer_records"
+]

Changed2 schema fields changedSep 13, 2026

addedOutput schema / properties / agent_context

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "customer_records": {
+      "type": "string"
+    },
+    "instructions": {
+      "type": "string"
+    },
+    "knowledge": {
+      "additionalProperties": false,
+      "properties": {
+        "instructions": {
+          "type": "string"
+        },
+        "missing_information": {
+          "type": "string"
+        },
+        "read_tool": {
+          "type": "string"
+        },
+        "search_tool": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "search_tool",
+        "read_tool",
+        "instructions",
+        "missing_information"
+      ],
+      "type": "object"
+    },
+    "locations": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "city": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "state": {
+            "type": "string"
+          },
+          "street": {
+            "type": "string"
+          },
+          "zip": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "street",
+          "city",
+          "state",
+          "zip"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "pricing": {
+      "additionalProperties": false,
+      "properties": {
+        "currency": {
+          "type": "string"
+        },
+        "dispatch_fee": {
+          "type": "number"
+        },
+        "estimates": {
+          "type": "string"
+        },
+        "policy": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "currency",
+        "dispatch_fee",
+        "policy",
+        "estimates"
+      ],
+      "type": "object"
+    },
+    "scheduling": {
+      "additionalProperties": false,
+      "properties": {
+        "after_hours": {
+          "type": "string"
+        },
+        "emergency": {
+          "type": "string"
+        },
+        "regular": {
+          "type": "string"
+        },
+        "routine": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "regular",
+        "after_hours",
+        "routine",
+        "emergency"
+      ],
+      "type": "object"
+    },
+    "service_area": {
+      "additionalProperties": false,
+      "properties": {
+        "exact_coverage_tool": {
+          "type": "string"
+        },
+        "summary": {
+          "type": "string"
+        },
+        "towns": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "summary",
+        "towns",
+        "exact_coverage_tool"
+      ],
+      "type": "object"
+    },
+    "services": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "name": {
+            "type": "string"
+          },
+          "summary": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "summary"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "timezone": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "instructions",
+    "timezone",
+    "locations",
+    "services",
+    "service_area",
+    "pricing",
+    "scheduling",
+    "knowledge",
+    "customer_records"
+  ],
+  "type": "object"
+}

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

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 readOnly/idempotent/non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral value by characterizing the content as static ('self-contained', 'without browsing the website') and by stating a negative boundary (not live availability, not private records), telling the agent this is a safe orientation call rather than a live-data probe.

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?

A single front-loaded sentence leads with 'Start here' and the payload scope, then closes with the exclusion. The middle content list is long but each item is load-bearing for routing decisions; nothing is redundant with the title or annotations.

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 detail is unnecessary, and the description still tells the agent what the return covers and, importantly, what it does not cover. For a zero-param entry-point tool among 15 siblings, the routing boundary and content inventory make this complete.

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?

The tool takes zero parameters, so there is nothing schema-wise for the description to compensate for; the 0-parameter baseline of 4 applies. The description correctly implies a parameterless, whole-business call by describing the payload as one self-contained briefing.

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 ('Get Business Information' / 'self-contained business briefing') and enumerates the concrete content buckets: locations, services, hours, service area, dispatch fee, pricing, booking policies, credentials, payment methods. The enumeration also implicitly separates it from siblings like get_services_pricing and check_service_area, which cover only a subset.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Start here' establishes this as the entry-point tool, and the closing clause 'Not live availability or private customer records' explicitly rules out the domains owned by get_availability and customer_lookup. No sibling is named directly, so routing is inferred rather than stated, which keeps it short of a 5.

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?