Skip to main content
Glama
chrischall

Housecall Pro MCP

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

housecallpro_decline_estimate

Destructive

Decline selected estimate options to let your contractor know you are not proceeding. A confirmation step prevents accidental changes, and the decline cannot be undone.

Instructions

Decline one or more options on an estimate. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call posts nothing and returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Declining tells the contractor you are not proceeding; it cannot be undone from here.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
linkNoThe Housecall Pro link your contractor sent you — paste it directly (pro.housecallpro.com/mobile_estimate/… or /mobile_invoice/…, or a client.housecallpro.com/estimates/… or /invoices/… URL), or the retrieval token from the end of it. Alternatively the label of a link configured in HOUSECALLPRO_LINKS. Omit only when exactly one link is configured.
option_idsYesEstimate option ids to decline, from `options[].id` (e.g. `est_…`).
confirmTokenNoONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 "confirmation-required" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.0
    • removedInput schema / properties / confirm
      Removed value: -{
-  "description": "Must be true to proceed. Without this, the tool returns a preview.",
-  "type": "boolean"
-}
    • addedInput schema / properties / confirmToken
      Added value: +{
+  "description": "ONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 \"confirmation-required\" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.",
+  "type": "string"
+}
  2. Changed1 schema field changedv0.4.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. First observedv0.2.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations include destructiveHint=true, but the description goes further by stating 'it cannot be undone from here' and explaining the confirmation mechanism in detail: a native confirmation prompt when supported, otherwise a two-step flow where the first call posts nothing and returns a preview and confirmToken. This transparently discloses the side effects and the fallback behavior. No contradiction with annotations.

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 composed of three well-focused sentences: the operation, the confirmation flow, and the irreversible consequence. It is front-loaded with the purpose and every sentence earns its place, including the important cross-reference to MCP_CONFIRM_MODE for the fallback path.

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?

For a destructive tool with a two-step confirmation fallback, the description covers both execution paths and explains what the first call returns (preview and confirmToken). It does not explicitly state what the final call returns or describe the success response, but given the protocol reference and the detail in the schema, it is sufficiently complete for an agent to invoke the tool correctly.

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 input schema already documents all three parameters with full descriptions at 100% coverage, including the nuanced confirmToken usage. The description adds no additional parameter-level semantics, so the baseline score of 3 is appropriate; it does not need to compensate for schema gaps.

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 the exact operation ('Decline one or more options on an estimate') and clarifies the semantic outcome ('Declining tells the contractor you are not proceeding'). This clearly differentiates it from the sibling housecallpro_approve_estimate, which performs the opposite action.

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 conveys when the tool is appropriate: when the user wants to decline an estimate option and does not intend to proceed. It also warns that the action cannot be undone, which is critical usage guidance. It does not explicitly name alternatives or exclusion conditions, but the purpose and consequence make the intended use obvious.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools