Skip to main content
Glama
Lucacelli B2B MCP Server

Lucacelli B2B MCP Server

Solar, HVAC, Roofing & Home Services Contractor Spy

find_solar_hvac_contractor_leads
Read-onlyIdempotent

Detect ServiceTitan, Housecall Pro, Jobber, financing widgets, license numbers, and owner contacts on solar, HVAC, plumbing, or roofing contractor websites to qualify and enrich B2B leads.

Instructions

Detect ServiceTitan, Housecall Pro, Jobber, financing widgets, license numbers, and owner contacts across home-service contractor websites ($0.80/1k).

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": {
      "domains": "<domains>"
    },
    "name": "find_solar_hvac_contractor_leads"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainsYesSolar, HVAC, plumbing, or roofing domains

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, openWorld, idempotent and non-destructive, so safety behavior is covered. The description adds a genuinely useful non-annotation fact: pricing at $0.80/1k. It says nothing about crawl depth (homepage vs. subpages), batching limits, failure behavior, or how many domains per call are practical, and there is no output schema to fall back on.

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?

A single dense sentence that leads with what gets detected and closes with the price, so no sentence is wasted. The parenthetical price placement is efficient. It is nearly as compact as possible for the content it carries.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter, annotation-rich, no-output-schema tool this is close to adequate, and enumerating the detected signals implicitly sketches the return shape. However, with no output schema the description could say a bit more about what a result record contains per domain and what crawl scope is used.

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?

Only one parameter, and schema coverage is 100% with the schema already listing 'Solar, HVAC, plumbing, or roofing domains' as examples. The description's mention of 'home-service contractor websites' adds marginal framing but no format or sizing guidance (URL vs. bare domain, list size) 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?

Names a concrete detection target set (ServiceTitan, Housecall Pro, Jobber, financing widgets, license numbers, owner contacts) applied to a specific vertical (home-service contractor websites). This distinguishes it clearly from the vertical siblings like dental, restaurant, or salon lead finders. Slight friction: the tool name says 'find leads' while the description emphasizes 'detect ... signals', so an agent must infer that detected signals equal leads.

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

Usage Guidelines2/5

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

No explicit statement of when to use this versus alternatives such as scrape_google_maps_leads or the other vertical lead finders, and no prerequisites or exclusions. Usage is only implied by the vertical naming ('home-service contractor websites'). An agent gets no routing rule beyond vertical matching.

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