Latchbell

Log a new lead

log_lead

Owners only (needs sign-in): Call this when a new lead arrives (e.g. a Thumbtack, Angi, Bark or Yelp lead email in Gmail, or a Facebook/Instagram message). Returns a firm quote, open times, and a reply draft. For platform leads (Thumbtack, Angi, Bark, Yelp, Google), the customer name and contact are not stored and the reply must be sent inside that platform; never send platform customers links to book elsewhere.

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": {
      "source": "<source>"
    },
    "name": "log_lead"
  }
}

Input Schema

Name	Required	Description	Default
`zip`	No
`pets`	No
`sqft`	No	Home size in square feet, only if the customer said it. Homes larger than usual for their bedroom count cost more; never guess
`issue`	No	Plumbing and heating & AC pros only, instead of bedrooms/bathrooms. plumbing: leak (Leak or drip), clog (Clogged drain or toilet), water_heater (Water heater), toilet (Toilet repair), fixture (Faucet, sink or fixture), no_water (Low or no water), other (Something else). hvac: no_cool (AC not cooling), no_heat (No heat), maintenance (Tune-up or maintenance), noise (Noise, smell or leak), thermostat (Thermostat), other (Something else)
`source`	Yes
`add_ons`	No
`contact`	No	Only for direct leads
`details`	No	Plumbing and heating & AC pros only: the problem in the customer's words
`bedrooms`	No
`lead_ref`	No	The platform's lead or request ID
`bathrooms`	No
`lead_cost`	No	What the platform charged, USD
`clean_type`	No	move_out also covers move-in. turnover = short-term rental (Airbnb/Vrbo) clean between guests	standard
`selections`	No	What they asked for, from your catalog, for a firm price and open times
`customer_first_name`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Goes well beyond the annotations: declares owner-only auth, describes what the call returns (firm quote, open times, reply draft), and discloses a significant domain constraint — platform lead contact data is not stored, and replies must be sent inside the platform, never with external booking links. That is exactly the kind of non-obvious behavior an agent would otherwise get wrong.

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 sentences, front-loaded with the auth prerequisite and the trigger, then the return value, then the platform caveat. Nearly every clause carries information; the parenthetical source list is long but earns its place by anchoring the trigger.

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?

With no output schema, the description usefully states the return payload (quote, open times, reply draft) and covers auth and the platform constraint. It leaves some gaps around failure modes and what to supply for non-platform/direct leads, but is largely sufficient to invoke correctly.

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 53% across 15 parameters, and the description only illuminates the platform-vs-direct contact distinction. Many fields (zip, pets, sqft, bedrooms, bathrooms, add_ons, selections, lead_cost, customer_first_name) get no explanation beyond the schema, so it partially but not fully compensates for the coverage gap.

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 (logging a new lead) and enumerates concrete triggering sources (Thumbtack/Angi/Bark/Yelp emails, Facebook/Instagram messages). It does not differentiate from siblings like update_lead or quote, even though it mentions producing a quote.

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?

Gives an explicit trigger condition ('when a new lead arrives') with real-world examples of what that looks like, plus an owner/sign-in prerequisite. It does not say what to call for existing leads or when to prefer quote/book instead of logging first.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

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

Resources

Need Help?