Skip to main content
Glama
Sign In

Housecall Pro MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Send invoice

send_invoice
Destructive

Email an invoice to the customer as a PDF with the company's default or your own message. Sends as the Send invoice dialog does, by email only. The customer gets it at once. By default you confirm each call; you can switch that off for this tool. Waits for the owner's approval.

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": {
      "invoice_id": "<invoice_id>"
    },
    "name": "send_invoice"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoSend to this address. Default: the customer's billing email.
messageNoEmail text. Default: the company's invoice message.
subjectNoDefault: the company's invoice subject.
invoice_idYesinvoice_id from list_invoices or get_job.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing that delivery is immediate and email-only, that a confirmation prompt fires by default and can be disabled per tool, and that the send waits for the owner's approval. The approval/auth requirement and the irreversible outbound side effect are exactly the facts an agent needs before calling a destructive, non-idempotent, open-world tool.

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?

Front-loads the core action and keeps to short sentences, with no filler. The closing 'By default you confirm each call; you can switch that off' and 'Waits for the owner's approval' overlap somewhat and could be merged, leaving mild redundancy.

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 four-parameter mutation tool with full annotation coverage and no output schema, the description covers channel, delivery timing, defaults, confirmation, and approval. It stops short of saying what happens on failure or whether the invoice's status changes afterward, which would matter for a destructive send.

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 coverage is 100%, so every parameter's meaning and default is already documented in the schema, which sets the baseline at 3. The description adds only a light restatement ('company's default or your own message') and no format, length, or override-precedence detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Email an invoice to the customer as a PDF') plus the channel constraint ('by email only'), which separates it from create/record-oriented siblings. It does not explicitly contrast with send_estimate or housecall_pro_send_invoice, so sibling differentiation is only partial.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied through 'Sends as the Send invoice dialog does, by email only' and the delivery/approval notes, giving an agent enough context to know this is the email-delivery path. However, there is no explicit when-to-use vs when-not guidance and no named alternative for other delivery channels or for creating an invoice first.

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