HireNimbus home services MCP

Get provider reviews

get_provider_reviews

Read-onlyIdempotent

Fetch reviews for a HireNimbus service provider by slug. Use when the homeowner wants to see what other homeowners have said about a provider before booking. Read-only; does not create a booking. 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
`slug`	Yes
`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."
`page_size`	No

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: -[
-  "slug",
-  "context"
-]New value: +[
+  "slug"
+]

First observedSep 16, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description's reinforcement of 'Read-only; does not create a booking' adds little. However, the description discloses the context parameter's optional-yet-required nature ('Always pass optional context', 'Omitting it does not fail the call; do not send an empty string') which is not covered by annotations. This is valuable behavioral nuance for the agent.

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

Conciseness5/5

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

The description is two sentences, tightly packed with the core action, usage context, and a behavioral note about the context parameter. It is front-loaded with the primary function and avoids any filler or redundant wording. Every clause contributes to agent decision-making.

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 that an output schema exists (so return format is covered), the description sufficiently explains the tool's purpose, when to use it, and the critical context parameter behavior. It does not describe pagination limits or results ordering, but those are inferable from parameter names and the output schema. The context quirk is well documented, making the tool callable correctly without additional assumptions.

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 description clarifies that `slug` identifies the provider ('by slug'), but the schema already provides a detailed description for `context` (which the description echoes). The pagination parameters `page` and `page_size` are not described in either the schema or the description, relying only on their names. With schema coverage at 25%, the description partially compensates for the missing parameter explanations but does not fully address pagination semantics.

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 explicitly states 'Fetch reviews for a HireNimbus service provider by slug,' which is a specific verb (fetch), resource (reviews), and identifier (slug). It is clearly distinguishable from sibling tools like booking (book_plumber) or provider info (get_provider_details) because it focuses solely on reviews. The purpose is unambiguous and action-oriented.

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 provides a clear use case ('Use when the homeowner wants to see what other homeowners have said about a provider before booking') and explicitly notes it is read-only and 'does not create a booking,' which helps avoid confusion with booking tools. However, it does not explicitly name alternative tools such as get_provider_details or search_providers, leaving some inference required about when to use those instead.

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.