Skip to main content
Glama

Emergency Plumbing Help

emergency_help
Read-onlyIdempotent

Use this immediately when the user describes an urgent plumbing safety or damage situation. Give bounded mitigation guidance and direct them to call Johnson Bros.; for gas, fire, or immediate danger, direct them to leave and call 911 first. Do not treat this tool as monitored emergency dispatch or create an online emergency appointment.

WHEN TO USE: Immediately when a customer mentions an emergency situation like:

  • Burst pipe, flooding, or water damage

  • Gas smell or suspected gas leak (CRITICAL - may need to call 911)

  • Sewage backup or overflow

  • No water or sudden loss of water

  • Water heater leaking or not working

PRIORITY ORDER:

  1. First ensure customer safety (especially for gas leaks)

  2. Provide immediate mitigation steps (how to shut off water, etc.)

  3. Then tell the user to call Johnson Bros. for emergency service

RETURNS: Step-by-step immediate actions, safety warnings, things NOT to do, urgency level, and whether emergency dispatch is recommended.

IMPORTANT: For gas leaks, always advise leaving the house and calling 911 first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emergency_typeYesType of plumbing emergency (required). Examples: 'burst pipe', 'flooding', 'gas leak', 'sewage backup', 'no hot water', 'no water'
additional_detailsNoAdditional context about the emergency (optional). Include location, duration, actions already taken.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNo
successYes
call_nowNo
urgency_levelNo
emergency_typeNo
recommendationNo
review_sandboxNo
immediate_stepsNo
safety_warningsNo
emergency_contactNo

TDQS

A4.7/5.0
Behavior5/5

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

The description aligns with annotations (readOnly, idempotent) and adds behavioral context: it describes the nature of the tool as giving bounded guidance and the output through the 'RETURNS' section. There is no contradiction with annotations.

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 concise and well-structured, with a clear directive, specific conditions, and a 'RETURNS' summary. It avoids unnecessary verbosity while covering essential aspects.

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?

The description is complete for the tool's scope: it covers purpose, usage, parameters, output, and edge cases (gas/fire). Given the tool's simplicity and existing schema coverage, no critical information 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 both parameters, including examples for emergency_type and guidance for additional_details. The description does not add further semantic detail beyond the schema, so it meets the baseline without enhancement.

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 a specific verb ('Use this immediately') and the resource ('urgent plumbing safety or damage situation'), and distinguishes it from sibling tools like booking and info tools by focusing on emergency guidance. It also provides explicit conditions for gas/fire/immediate danger, making the purpose unambiguous.

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 explicitly states when to use (for urgent plumbing safety/damage) and what to do (bounded mitigation guidance, direct to call Johnson Bros., and for gas/fire/immediate danger, leave and call 911). It also excludes using it for monitored emergency dispatch or online appointment creation, clarifying boundaries relative to siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation4/5

Most tools have clear, distinct purposes: business_info vs search vs get_services_pricing are separable. However, get_services_pricing and get_quote overlap somewhat—both provide pricing info, though one is for general browsing and the other for specific estimates. The descriptions do help distinguish them, so the ambiguity is low.

Naming Consistency4/5

Tool names generally follow a verb_noun pattern (e.g., business_info, check_service_area, confirm_booking, get_availability, get_quote). Some names are single verbs or nouns (e.g., fetch, search) which deviate slightly, but overall the pattern is consistent and predictable.

Tool Count5/5

11 tools is within the ideal range for a booking-focused MCP server. Each tool covers a distinct part of the customer journey: info lookup, service area check, pricing, availability, booking, confirmation, callbacks, emergencies, and document retrieval. No tool seems redundant or unnecessary.

Completeness4/5

The tool set covers the core booking lifecycle: check service area, get availability, request booking, confirm booking, request callback, and get quotes. Emergency help is also provided. Minor gaps include lack of a cancel/update booking tool, but the server context suggests that might not be needed for the public-facing purpose.

Resources