Skip to main content
Glama
Sign In

Housecall Pro MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Cotlet: how to work in an app

cotlet_app_guide
Read-onlyIdempotent

How to work in an app by clicking in the user's Cloud Browser with Cotlet's browser tools: which browser to use for this workspace and the sign-in link, the method step by step, the app's screens, menus and actions, notes, and the app's dedicated tools when Cotlet has them. Call it before the first browser step in an app. Works for any web app; one outside Cotlet's catalog gets the general method. Free, no browser session. For Housecall Pro it covers these actions: Create job, Create estimate, Create invoice, Send invoice, List customers.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cotlet_app_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
appNoThe app's name or Cotlet slug. Default: Housecall Pro.
taskNoWhat the user wants done in the app, in their words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so safety is covered. The description adds genuinely new behavioral facts: it is free, it does not consume a browser session, and it degrades gracefully for uncatalogued apps. It does not say whether the guidance is cached or whether repeated calls are cheap after the first, which is the main remaining unknown.

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

Conciseness3/5

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

The call instruction and cost note are front-loaded, which is good, but the central sentence is a long comma-spliced inventory ('which browser to use... the method step by step, the app's screens, menus and actions, notes, and the app's dedicated tools') that reads as a run-on rather than a scannable list. Nothing is strictly wasted, but the density hurts fast parsing.

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 two-optional-parameter read tool with no output schema, the description covers when to call it, what it returns in kind, the cost profile, and the fallback behavior for unknown apps, plus a concrete coverage example (Housecall Pro actions). Only the shape of the returned guidance and whether per-app detail varies in length are unspecified, a minor 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 coverage is 100%, so both 'app' and 'task' are already documented, including the Housecall Pro default. The description reinforces that the app may be a name or a Cotlet slug and that it is optional, but adds no format or syntax detail beyond the schema. Baseline 3 applies.

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?

The description states a specific, unusual resource: guidance on how to drive a web app through the Cloud Browser, naming the concrete content returned (which browser, sign-in link, method, screens, menus, actions, app-specific tools). It is clearly distinguishable from the cotlet_browser_* action tools, which perform the clicks this tool only explains. It stops short of 5 because 'how to work in an app' is framed as a verb phrase rather than stating plainly that it returns instructions.

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?

'Call it before the first browser step in an app' gives an explicit trigger point rather than a vague suggestion, and 'works for any web app; one outside Cotlet's catalog gets the general method' tells the agent it does not need to pre-check catalog membership. No explicit when-not-to-use case is given (e.g. don't re-call for every step in the same app), which keeps it off a 5.

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