Skip to main content
Glama

HireNimbus home services MCP

Book HVAC

book_hvac
Read-onlyIdempotent

Searches HireNimbus providers for HVAC heating, cooling, or AC service, including jobs 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. Does not require authentication. Inputs include a 5-digit US ZIP location, page, limit, and optional context. Returns provider records and resolved location. Read-only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "location": "<location>"
    },
    "name": "book_hvac"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNo
contextNoOptional analytics context for a brief, non-identifying summary of the request purpose. The value is recorded as Agent Intent.
locationYes5-digit US ZIP code (e.g. "22307" or "94114").

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / context / description
      Previous 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.\""New value: +"Optional analytics context for a brief, non-identifying summary of the request purpose. The value is recorded as Agent Intent."
    • changedInput schema / properties / location / description
      Previous value: -"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."New value: +"5-digit US ZIP code (e.g. \"22307\" or \"94114\")."
  2. Changed7 schema fields changed
    • 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"
      +]
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered; the description adds the non-obvious operational fact that no authentication is required and that results include provider records plus resolved location. The trailing 'Read-only.' merely restates the annotation and earns nothing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening verb+resource is front-loaded correctly, but the middle sentence is a sprawling run-on list of ~12 job phrases that reads as keyword stuffing rather than prose. The closing 'Read-only.' duplicates the annotation and could be dropped without loss.

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-shape detail is unnecessary, and auth, scope and matching contexts are all stated for a 4-parameter read-only search. Nothing an agent needs to invoke this correctly is missing, aside from optional sibling-routing guidance.

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?

At 50% schema coverage the schema already documents location and context, and the description only enumerates 'a 5-digit US ZIP location, page, limit, and optional context' without explaining pagination behavior, defaults (page=1, limit=6), or the Agent Intent recording semantics that context carries. It adds naming value over the schema but nothing that changes how an agent sets page or limit.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource: 'Searches HireNimbus providers for HVAC heating, cooling, or AC service', and enumerates concrete job types that an agent can match against a homeowner request. It never distinguishes itself from the sibling find_hvac, and the name/title ('book_hvac', 'Book HVAC') implies a booking action while the description describes a read-only search, which slightly muddies identification.

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?

The long list of qualifying jobs (AC not cooling, furnace won't start, thermostat install, tune-up, mini-split, duct sealing, uneven room temps) gives an agent a clear picture of when to reach for this tool. It offers no exclusions and never names an alternative such as find_hvac, so routing between the near-identical search siblings is left to inference.

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.