HireNimbus home services MCP

Search providers

search_providers

Read-onlyIdempotent

Use this when the user needs a home service outside the five dedicated find_* categories — such as house cleaning or deep cleaning, landscaping, lawn care or mowing, tree trimming, roofing or roof leak repair, gutter installation, pressure washing, junk removal, moving help, painting, or pest-adjacent cleanup — or when the service category is ambiguous. Prefer a 5-digit US ZIP for location (e.g. "22307", "94114"); never a street address, formattedAddress, or address1. Read-only; does not create a booking. Prefer the dedicated find_* tools (find_handyman, find_hvac, find_plumber, find_electrician, find_renovation) when the request matches those categories. Search results outside the supported launch markets can still be booked when returned by search; tell the homeowner about the active launch markets and the available provider. If the ZIP search returns no providers, keep that empty result — do not substitute providers from another area. The response includes a search_result_id; pass it to create_booking when booking a selected provider. 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
`query`	Yes	Service keyword for non-top categories (e.g. cleaning, landscaping, roofing). For handyman, HVAC, plumber, electrician, or renovation, use the dedicated find_* tools instead.
`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: -[
-  "query",
-  "location",
-  "context"
-]New value: +[
+  "query",
+  "location"
+]

First observedSep 16, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior, but the description adds valuable behavioral context: no booking creation, launch-market booking caveats, preserving empty results, the search_result_id contract for create_booking, and the context analytics requirement. This goes well beyond annotation coverage.

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 dense but well organized, front-loading the use case before caveats. Some statements repeat information already in the schema or annotations, such as read-only status and ZIP preference, so it is not maximally concise, but every sentence carries useful decision or safety content.

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?

Given the output schema exists and the sibling set is rich, the description covers the critical decisions: when to use this tool, when to defer to find_* tools, location constraints, empty-result behavior, booking integration, and analytics context. An agent has enough to call it correctly and avoid common mistakes.

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

Parameters4/5

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

With 60% schema description coverage, the description adds meaningful parameter context: it reinforces the preferred 5-digit ZIP format, forbids street addresses, and clarifies that context should always be passed but that omitting it will not fail the call. It doesn't detail page or limit, but those have schema defaults and are lower-risk.

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 defines the tool as the general home-services search for anything outside the five dedicated find_* categories, with concrete examples like cleaning, landscaping, and roofing. It also names the sibling find_* tools it is not, so an agent can disambiguate without opening schemas.

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 this tool versus the find_* alternatives, including the ambiguous-category case. It also gives specific location guidance, warns against street addresses, and instructs not to substitute providers for empty results—strong, actionable routing.

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.