Skip to main content
Glama
chrischall

Housecall Pro MCP

by chrischall
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

housecallpro_get_estimate

Read-only

Retrieve a Housecall Pro estimate from a contractor link to review line items, totals, tax, company details, and whether it still awaits your approval.

Instructions

Read an estimate a Housecall Pro contractor sent you: line items, totals, tax, the company behind it, and whether it is still awaiting your approval. The default compact view returns money both as integer cents (*_cents, verbatim from the API) and as dollars (*_usd); view: "raw" returns the upstream document, whose money is cents only.

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.
viewNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "raw" returns the upstream payload unprojected. "compact" is the summary: line items, totals, tax, company and approval state, with every money field as both `*_cents` and `*_usd`. "raw" is the upstream document (~4.8 KB, mostly display flags and `{object, data}` wrappers) — its money is integer CENTS with no dollar sibling, so `total_amount: 34639` means $346.39.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changedv0.3.0
    • removedInput schema / properties / raw
      Removed value: -{
-  "description": "Return the full upstream document instead of the summary. Much larger, and mostly display flags.",
-  "type": "boolean"
-}
    • addedInput schema / properties / view
      Added value: +{
+  "description": "Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"raw\" returns the upstream payload unprojected. \"compact\" is the summary: line items, totals, tax, company and approval state, with every money field as both `*_cents` and `*_usd`. \"raw\" is the upstream document (~4.8 KB, mostly display flags and `{object, data}` wrappers) — its money is integer CENTS with no dollar sibling, so `total_amount: 34639` means $346.39.",
+  "enum": [
+    "compact",
+    "raw"
+  ],
+  "type": "string"
+}
  2. First observedv0.2.0

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnlyHint, the description discloses important behavior: the default compact view returns money as both integer cents and dollars, while raw returns the upstream document with cents-only money. It also warns about the cents interpretation, preventing misreading of raw values.

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?

Two dense sentences with no filler. The main purpose is front-loaded, and the view-format nuance is presented in a compact, easy-to-scan second sentence.

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?

The description, combined with a fully documented schema and readOnly/openWorld annotations, gives an agent everything needed to call the tool correctly. It covers the return contents, money representation, and the two views without requiring an output schema.

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?

Schema description coverage is 100% and both parameters already have detailed schema descriptions. The tool description adds little beyond what the schema provides, so the baseline of 3 is appropriate.

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?

Description uses a specific verb ('Read') and resource ('an estimate'), and lists the concrete contents returned: line items, totals, tax, company, and approval state. It clearly distinguishes itself from sibling tools like housecallpro_get_invoice and the approve/decline actions.

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 makes the intended use clear: reading an estimate a contractor sent, including its approval status. It does not explicitly name alternatives or exclude invoices, but the resource type and sibling names make the selection unambiguous.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/chrischall/housecallpro-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server