Skip to main content
Glama
Lucacelli B2B MCP Server

Lucacelli B2B MCP Server

B2B Company Domain Email, Phone & Tech Enricher

enrich_b2b_company_domain
Read-onlyIdempotent

Enrich company domains with verified emails, phone numbers, LinkedIn/X/Instagram handles, DNS MX/SPF/DMARC records, and SaaS tech stack signatures to support B2B lead research and outreach.

Instructions

Enrich company domains with verified emails, phone numbers, LinkedIn/X/Instagram handles, DNS MX/SPF/DMARC records, and 38+ SaaS tech stack signatures ($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": "enrich_b2b_company_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainsYesCompany domains, e.g. ["stripe.com", "linear.app"]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

B3.4/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 behavior is covered elsewhere. The description adds useful context by naming output data categories and pricing ($0.80/1k), but it does not explain rate limits, error handling for invalid domains, or output structure.

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 a single front-loaded sentence with no filler. Every listed data category and the pricing note contribute to helping an agent understand the enrichment output.

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 enrichment tool with rich annotations, the description lists the main enriched outputs and cost. It is close to complete, though it does not specify response shape, handling of invalid or missing domains, or whether results are returned per domain.

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 only one parameter and schema description coverage is 100%, so the schema already explains the domain array with examples. The description's mention of 'company domains' aligns with the parameter but adds no syntax, format, or batching detail 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?

The description states a specific verb and resource: enrich company domains. It lists concrete enriched data types (emails, phones, social handles, DNS records, tech stack), so the tool's purpose is clear. It does not explicitly differentiate itself from sibling tools such as build_360_b2b_company_dossier.

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?

The description gives no when-to-use or when-not-to-use guidance, no prerequisites, and no explicit alternatives. An agent can infer that it applies to known company domains, but there is no routing guidance against adjacent enrichment or dossier-building siblings.

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