HireNimbus home services MCP

Cancel booking

cancel_booking

DestructiveIdempotent

Cancel one of the authenticated homeowner's bookings. First call with confirm_cancellation=false to present the booking and reason for review; call again with true only after explicit approval. The cancellation reason is delivered to the provider.

Input Schema

TableJSON Schema

Name	Required	Description
`job_id`	Yes	Booking ID from get_previous_jobs
`reason`	Yes	Short homeowner-provided cancellation reason
`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."
`confirm_cancellation`	No	false (default): return a cancellation preview without changing the booking; true: cancel after the homeowner explicitly confirms

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 16, 2026

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."
+]

changedInput schema / required

Previous value: -[
-  "job_id",
-  "reason",
-  "context"
-]New value: +[
+  "job_id",
+  "reason"
+]

First observedSep 16, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds crucial behavioral context: the first call is a non-destructive preview, and the second call actually cancels. It also discloses that the cancellation reason is sent to the provider, a side effect beyond what annotations convey.

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, with the core action and two-step flow front-loaded. It conveys all essential operational details without redundancy or filler, achieving high information density in a compact format.

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 destructive two-step action, the description covers the entire workflow: preview, approval, cancellation, and side effect. The presence of an output schema handles return values, so nothing an agent needs to invoke this tool correctly is missing.

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?

Schema coverage is 100%, but the description adds significant value by emphasizing that the context parameter is mandatory on every call and explaining its purpose and format. It also clarifies the semantic difference between confirm_cancellation=false (preview) and true (cancel), which the schema's default description implies but the description makes explicit.

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 states a specific verb ('Cancel') and resource ('one of the authenticated homeowner's bookings'), and it distinguishes itself from all sibling tools (no other cancel tool exists). It also clarifies the two-step process, making the purpose unambiguous.

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?

The description explicitly instructs the agent to first call with confirm_cancellation=false to present a preview, then call again with true only after explicit approval. It also mandates the always-include context argument and warns that the reason is delivered to the provider, giving clear usage direction.

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.