Skip to main content
Glama
Lucacelli B2B MCP Server

Lucacelli B2B MCP Server

Accounting, CPA & Tax Advisory Firm Lead Enricher

find_accounting_cpa_firm_leads
Read-onlyIdempotent

Extract partner emails, client portal software, and phone numbers from CPA and accounting firm domains to build targeted B2B lead lists.

Instructions

Extract partner emails, client portal software (CCH, Thomson Reuters, QuickBooks, Xero, Canopy), and phone numbers from CPA and accounting firm domains ($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_accounting_cpa_firm_leads"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainsYesAccounting or CPA firm domains

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety and repeatability are covered. The description adds two genuinely useful facts beyond that: cost ($0.80 per 1k domains) and the concrete fields returned. It does not say what happens for domains with no match, whether missing fields are omitted or null, or whether there are rate/volume limits, so it stays at an adequate 3.

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?

One tightly packed sentence with the output fields front-loaded and the cost annotation at the end; nothing is padded. It is slightly list-heavy (vendor names in parentheses) and has no usage sentence, but it wastes no words.

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 one-parameter extraction tool with full annotation coverage and no output schema, the description does the important remaining work: it names the returned data so the agent knows what comes back, and it discloses pricing. Only the edge behavior for non-matching or partially matching domains is left unstated.

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?

There is a single required parameter, domains, and the schema description coverage is 100% ("Accounting or CPA firm domains"), so the schema already carries the semantics. The description's phrase "from CPA and accounting firm domains" reinforces the input constraint but adds no format, batching, or validation 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ("Extract") plus enumerated outputs (partner emails, client portal software by vendor name, phone numbers) and a narrow target population (CPA and accounting firm domains). That combination of output fields and vertical makes it clearly distinguishable from the sibling enrichers like find_dental_medical_clinic_leads or scrape_google_maps_leads.

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

Usage Guidelines3/5

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

The niche restriction and the named extractable fields imply when this tool fits (accounting/CPA verticals needing partner contacts and tech stack), but there is no explicit when-to-use or when-not guidance and no sibling is named as an alternative. An agent must infer the routing decision from the vertical alone.

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