Skip to main content
Glama
hcpapi

io.github.hcpapi/housecall-pro-mcp

by hcpapi

hcp_api_notes

Read-onlyIdempotent

Check the real behavior of Housecall Pro API endpoints—documentation may list routes that don't exist, writes that are silently ignored, or misleading field units. Use this lookup before retrying a 404 or declaring something impossible.

Instructions

Look up what the Housecall Pro API actually does for a given topic, as opposed to what its published documentation says. Call this BEFORE concluding that something cannot be done, before retrying a route that returned 404, and after any write that reported success but looks like it changed nothing. It answers from a table of verified behaviour: routes the documentation describes that do not exist, writes that are accepted and silently ignored, and fields whose units are not what they appear to be. Ask in plain words - a topic, a route, a field name, or the thing you were trying to do. Omit the topic to read the whole table. This tool reads a table compiled into this server and makes no API call, so it costs nothing and cannot fail.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicNoWhat you are working on. A route ("PATCH /jobs"), a field ("work_status"), or a goal ("set a job description", "create an invoice"). Omit for everything.
Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds further context by revealing that the tool makes no API call, reads a local compiled table, costs nothing, and cannot fail. This enriches the behavioral profile beyond the annotations without contradicting them.

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?

The description is long but every sentence delivers crucial guidance: purpose, when to call, content of the table, how to phrase queries, and the no-cost/no-fail guarantee. It is front-loaded with the core purpose and structured logically, with no filler.

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?

Given a single optional parameter, rich annotations, and no required output schema, the description fully explains what the tool does, what it contains, and what to expect. It leaves no significant gaps for an agent to misuse it.

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?

The schema already provides a thorough description for the single 'topic' parameter, including examples and the omission rule. The description's mention of 'plain words' is redundant with the schema's guidance. With 100% schema coverage, the description adds no meaningful parameter semantics beyond what the schema already offers.

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 unique purpose: looking up verified behavior of the Housecall Pro API versus its published docs. The verb 'look up' combined with the resource (verified behavior table) distinguishes it from sibling tools like hcp_get_business_profile or hcp_set_business_profile, which make actual API calls.

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?

Explicitly instructs when to use the tool: before concluding something cannot be done, before retrying a 404, and after a write that appears to have no effect. Also provides alternatives by contrasting with published documentation, making the use cases unmistakable.

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