HireNimbus home services MCP

Book electrician

book_electrician

Read-onlyIdempotent

Use when the user wants to book or hire a electrician — including when they describe a problem to fix, such as a dead outlet or outlet not working, breaker that keeps tripping, electrical panel upgrade, light fixture or ceiling fan installation, dimmer or switch replacement, EV charger installation, flickering lights, GFCI outlets, recessed lighting, hardwired smoke detectors, or exterior and landscape lighting. Runs the provider search first (query='electrician' 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.1/5.0

Behavior4/5

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

The annotations already signal read-only, open-world, idempotent, and non-destructive behavior. The description adds valuable behavioral context beyond that: it runs the provider search first with query='electrician' prefilled, it should not start OTP until create_booking returns auth_required, and omitting the context parameter does not fail the call. These details give the agent a clearer model of side effects and sequencing.

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 dense; it front-loads the core intent and example triggers before procedural guidance. Almost every sentence adds unique information, though the same point about context is made both in the description and the schema, slightly inflating length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema exists and the annotations cover safety semantics, the description is nearly complete. It explains the full workflow, when to stop for OTP, exclusions, and the required context format. The only minor gap is pagination behavior (page/limit), but defaults exist and the main flow is fully specified.

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 covers location and context with detailed descriptions, but page and limit have only defaults and no explanation. With 50% schema coverage, the description partially compensates by restating and expanding context requirements (15-25 words, third person, no PII, omit is allowed) and by emphasizing location should be a 5-digit ZIP. It does not add any semantics for page or limit, leaving pagination behavior implicit.

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 opens with a specific use case ('book or hire a electrician') and enumerates many example problems (dead outlet, breaker tripping, EV charger, etc.), making the tool's purpose unmistakable. It clearly distinguishes itself from siblings by explaining that it runs a provider search and then defers actual booking to create_booking.

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 description gives explicit conditions for use, including a long list of qualifying scenarios and an explicit exclusion: 'Do not use for DIY how-to advice or price research with no hiring intent.' It also outlines the sequence of steps (provider search → ask which pro → create_booking). It doesn't explicitly name find_electrician as the alternative for search-only intent, which would make it even clearer, but the exclusion plus process guidance is strong.

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.