Skip to main content
Glama
hcpapi

io.github.hcpapi/housecall-pro-mcp

by hcpapi

hcp_set_business_profile

Idempotent

Define or update business profile sections (shop, vendors, pricing, payroll, comms) for this installation. Each call replaces a whole section; null clears it, and data stays local.

Instructions

Store one or more business-profile sections for this installation: shop, vendors, pricing, payroll, comms. Each section replaces the stored section whole, and null clears one - so save a section only after reading the whole section back to the user for a yes. The profile is this installation's own file, on this machine, beside the defaults file. Nothing in it is read from Housecall Pro or sent to it, or to anyone else. The sections hold the shop's own facts, never a customer's, and never credentials: a vendor's account_hint refuses anything that looks like a full account number.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
shopNoWho the shop is: trade(s), region, team size, and any peer group they benchmark against. Pass null to clear the section.
commsNoHow outbound messages should sound: sender name, a short voice sample in the shop's own tone, and the follow-up cadence in days. Pass null to clear the section.
payrollNoPayroll rules: when the pay week starts and the commission rules by role. Pass null to clear the section.
pricingNoPricing rules: the margin floor, per-category overrides, and how prices are rounded. Pass null to clear the section.
vendorsNoWho they buy from: vendor name, a shipped pack name when one matches, how purchase documents arrive, an account hint (never a full number), and any learned custom layout. Pass null to clear the section.
Behavior1/5

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

The description contradicts the destructiveHint annotation. It states 'null clears one' section, which is a destructive operation, while annotations declare destructiveHint=false. This is a direct contradiction, and per the rules, transparency is scored 1.

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?

Four sentences pack significant information: purpose, replacement/clearing behavior, storage location, and privacy/security constraints. Every clause earns its place, though it could be slightly tightened.

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 fully covers the tool's behavior: what it stores, how sections are replaced/cleared, where the profile lives, and what it never contains. For a setter with no output schema, this is comprehensive and equips an agent for safe invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already describes all five parameters (100% coverage). The description adds crucial semantics beyond the schema: null clears a section, and vendor's account_hint rejects full account numbers. This enriches parameter understanding.

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 clearly states the tool's function: 'Store one or more business-profile sections for this installation' and names all five sections. It distinguishes itself from the sibling hcp_get_business_profile by focusing on writing/updating, not reading.

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?

It provides a critical usage guideline: 'save a section only after reading the whole section back to the user for a yes.' It does not explicitly name alternatives, but the contrast with hcp_get_business_profile is implicit. The privacy statement also informs when to use.

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/hcpapi/housecall-pro-mcp'

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