Skip to main content
Glama
Sign In

Housecall Pro MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Create estimate

create_estimate
Destructive

New estimate for a customer with its first option (Option #1) and lines. Sends nothing. Add more options with add_estimate_option, then email it with send_estimate.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "customer_id": "<customer_id>",
      "line_items": "<line_items>"
    },
    "name": "create_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageNoMessage to the customer shown on the estimate.
address_idNoService address of the customer (create_customer). Default: the billing address.
line_itemsYesLines of the first option, in order.
customer_idYescustomer_id from list_customers.
employee_idsNoEmployees to assign (list_employees). Default: none.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations declare destructiveHint=true and openWorldHint=true, and the description usefully qualifies that by clarifying nothing is sent to the customer at creation time — a genuine behavioral fact not encoded in the annotations. It stops short of noting whether the created estimate is a draft, what permissions are needed, or what happens if customer_id is invalid.

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?

Three short sentences, front-loaded with the creation scope, followed by the non-sending caveat and next steps. No redundant restatement of the title and no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a create tool with no output schema, the description never indicates what is returned — notably the estimate identifier the agent would need to chain into add_estimate_option or send_estimate. It covers the forward workflow names but leaves the handoff data implicit, which is the main completeness gap.

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%, so every field including line_items sub-fields, address_id defaults, and employee_ids is already documented in the schema. The description only restates that line_items are the 'lines of the first option, in order' rather than adding new meaning or validation constraints.

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?

States a specific verb and resource (creates a new estimate) plus the exact payload shape it produces: customer, Option #1, and its lines. The phrasing 'its first option (Option #1)' distinguishes it from add_estimate_option without the agent needing to open any schema.

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?

Gives explicit sequencing: use this tool first, then add_estimate_option for additional options, then send_estimate to email. It also states the exclusions ('Sends nothing'), so the agent knows this call alone does not deliver anything to the customer.

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

All Housecall Pro MCP Server and API by Cotlet toolsInspect
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.

Resources