---
name: agentnet-booking
description: "Arrange a customer-approved service request or inquiry with Mountain Man Plumbing using its enabled public tools. Use when the customer wants to contact or request service from this business."
---

# Arrange service with Mountain Man Plumbing

Read the [current schemas](https://mtnmanplumbing.com/?agentnet=actions) and [transport instructions](https://mtnmanplumbing.com/?agentnet=docs). Use direct HTTP or an already connected MCP client. These instructions do not install a connector or authorize a submission.

If a relevant page URL is known, read its Markdown alternate directly. Use search_pages only to find an unresolved page. Preserve exclusions and cite the human source.

Use get_booking_services to resolve a real service ID and read online coverage/fee terms when needed. A title or slug is not a service ID. If the task has no matching service, use the available office contact path.

Use get_availability with a real service_id and the customer's ZIP; supply a date when requested. State the timezone, observation time and fee conditions. No openings and a failed read are different outcomes. A valid offer is not a capacity hold.

Before request_booking, obtain the customer's approval of the selected service/window, contact/address details and disclosed fee. Use a fresh offer_token and the required schema fields. A changed or expired offer requires another availability read and renewed choice. Report pending office confirmation when that is the returned state.

Use submit_contact only for a message the customer has approved. Send contact details in the POST body, not a public URL.

Public submissions use the same CRM intake as human forms. No login or API key is required. User confirmation records the caller's assertion of approval; it is not identity verification. Use the same request_id and identical payload on retries. For outcome_unknown, stop and ask the office. Report the actual receipt, never a confirmed appointment.