Housecall Pro MCP Server and API by Cotlet

Create progress invoice

create_progress_invoice

Destructive

Invoice part of a job (an amount or a percent of its total); the rest stays to invoice later. Adds an invoice to the job as Invoice > Add invoice does with progressive invoicing on. Without amount or percent it bills everything left. Sends nothing: email it with send_invoice.

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": {
      "job_id": "<job_id>"
    },
    "name": "create_progress_invoice"
  }
}

Input Schema

Name	Required	Description
`due`	No	Payment terms: upon receipt, or net_days after the invoice date. Default: upon_receipt.
`amount`	No	Amount to bill in dollars.
`job_id`	Yes	job_id from list_jobs.
`percent`	No	Or a percent of the job total. Default (neither): all that is left to invoice.
`net_days`	No	Days for net. Default: 30.
`invoice_date`	No	YYYY-MM-DD. Default: today.
`reference_number`	No	Customer reference (PO) number.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context beyond that: no notification is sent, the remaining balance persists, and the no-argument default bills the entire remaining total (a consequential default for a destructive tool). It does not address retry/duplicate behavior, which matters given idempotentHint=false.

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

Conciseness4/5

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

Three short sentences, front-loaded with the scope-defining clause, then behavior, then the 'sends nothing' caveat. The parentheticals are dense but every clause carries information; the UI analogy ('as Invoice > Add invoice does') is a small cost for readers without the product.

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 7-parameter mutation with no output schema, the description covers scope, defaults, non-delivery, and the follow-up tool. It stops short of stating permission requirements or what happens when the requested amount exceeds the remaining balance, but that is a minor gap against otherwise solid coverage.

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 each parameter including amount, percent, and the net/due coupling is already documented, establishing a baseline of 3. The description reinforces the amount/percent/default relationship but adds no syntax or format detail the schema lacks.

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 ('Invoice part of a job') plus the partial-billing scope ('an amount or a percent of its total; the rest stays to invoice later'). It also distinguishes itself from send_invoice by declaring 'Sends nothing', so an agent can separate creation from delivery without opening either 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 conditional behavior: partial billing when amount/percent are supplied, 'bills everything left' when neither is. It names the follow-up alternative and the condition that selects it ('email it with send_invoice'), leaving nothing to inference.

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 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.