HireNimbus home services MCP

Book HVAC

book_hvac

Read-onlyIdempotent

Use when the user wants to book or hire a HVAC — including when they describe a problem to fix, such as AC not cooling or blowing warm air, furnace won't turn on or no heat, heat pump repair or installation, thermostat or smart-thermostat installation, refrigerant recharge, seasonal HVAC tune-up or maintenance, mini-split installation, duct sealing or cleaning, strange noises or smells from the unit, or uneven temperatures between rooms. Runs the provider search first (query='hvac' prefilled); after results, ask which pro they would like to book, then use create_booking. Do not start OTP until create_booking returns auth_required after they chose a pro. Do not use for DIY how-to advice or price research with no hiring intent. Always pass optional context on this call (15-25 words, third person, abstract purpose only, no PII) so analytics can record why the tool was called. Omitting it does not fail the call; do not send an empty string.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No
`limit`	No
`context`	No	Always include this argument on every call — do not omit it (analytics / Agent Intent). Write 15-25 words in third person explaining why this tool is being called. Abstract purpose only: never names, phones, emails, street addresses, IDs, or other PII. Example: "Homeowner wants vetted local plumbers for a leaking kitchen faucet within the previously confirmed ZIP."
`location`	Yes	Prefer a 5-digit US ZIP for location (e.g. "22307" or "94114"). This is the primary and preferred location input. After get_my_profile, if address.postalCode exists and the user confirmed the saved street address is the job site, pass that postalCode. Do not pass search_location when it is City, ST and a ZIP is available on the address. Never pass a street address, formattedAddress, or address1.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedSep 16, 2026

addedInput schema / properties / context / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / context / default
```
Added value: +null
```

changedInput schema / properties / context / description

Previous value: -"Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""New value: +"Always include this argument on every call — do not omit it (analytics / Agent Intent). Write 15-25 words in third person explaining why this tool is being called. Abstract purpose only: never names, phones, emails, street addresses, IDs, or other PII. Example: \"Homeowner wants vetted local plumbers for a leaking kitchen faucet within the previously confirmed ZIP.\""

addedInput schema / properties / context / examples

Added value: +[
+  "Homeowner wants vetted local plumbers for a leaking kitchen faucet within the previously confirmed ZIP.",
+  "Homeowner is comparing HVAC pros after a no-cool air conditioner at the confirmed job site."
+]

addedInput schema / properties / context / title
```
Added value: +"Context"
```
removedInput schema / properties / context / type
```
Removed value: -"string"
```

changedInput schema / required

Previous value: -[
-  "location",
-  "context"
-]New value: +[
+  "location"
+]

First observedSep 16, 2026

TDQS

A4.9/5.0

Behavior5/5

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

The description reveals that the tool itself only runs the provider search (read-only), and the actual booking is delegated to create_booking. It also discloses the OTP timing, the requirement to always pass context (with 15-25 word format), and that omitting context does not fail the call. This adds significant value beyond the readOnlyHint annotation, clarifying the non-destructive nature and the intended sequence.

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?

The description is long but every sentence is purposeful: it enumerates problem types, gives workflow steps, and specifies parameter details. It is well-structured, starting with the primary use case and then proceeding to constraints and execution. A minor deduction for verbosity—the list of scenarios could be trimmed without loss—but it remains highly functional.

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?

For a tool that orchestrates a multi-step booking flow, the description covers all essential aspects: when to invoke, what the tool returns (provider list), how to proceed (ask which pro, then create_booking), OTP handling, and parameter specifics. The presence of an output schema relieves the need to describe return values. Nothing critical is missing.

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

Parameters5/5

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

The description gives detailed, actionable guidance for the two complex parameters: location (prefer ZIP, never street address, use postalCode from profile) and context (15-25 words, third person, no PII, with examples). Page and limit have defaults and are self-explanatory, so the lack of description is acceptable. This compensates well for the 50% schema 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 clearly states the tool's purpose: booking or hiring an HVAC pro, with a long list of concrete problem scenarios (AC not cooling, furnace won't turn on, etc.). It distinguishes itself from sibling tools by focusing on HVAC and explicitly naming the alternative workflow (create_booking) for the actual booking.

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?

It explicitly states when to use ('Use when the user wants to book or hire a HVAC') and when not to ('Do not use for DIY how-to advice or price research with no hiring intent'). It also provides a step-by-step workflow (run provider search, ask which pro, then create_booking) and specifies not to start OTP prematurely. This is exemplary guidance.

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

All HireNimbus home services MCP 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.