Skip to main content
Glama
Lucacelli B2B MCP Server

Lucacelli B2B MCP Server

360° B2B Company Intelligence Dossier Builder

build_360_b2b_company_dossier
Read-onlyIdempotent

Generate a full 360-degree B2B company dossier from domains, combining executive contacts, DNS and security posture, ad spend pixels, and tech stack for lead research and account qualification.

Instructions

Generate a complete 360-degree B2B company intelligence dossier combining executive contacts, DNS/security posture, ad spend pixels, and tech stack ($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": "build_360_b2b_company_dossier"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainsYesTarget company domains

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description contributes one genuinely new fact — the ($0.80/1k) cost — but says nothing about how a multi-domain batch behaves, how long an aggregation over four data sources takes, or what happens when a domain has no DNS or pixel data. For a tool that fans out across several external sources, that's a meaningful gap.

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 front-loaded sentence, no filler, with the scope ('complete 360-degree') leading and the cost annotation appended so the agent sees price before committing. Slightly dense in its comma-separated component list, but every element conveys what the dossier contains.

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?

A read-only, single-parameter tool with no output schema — so the description should compensate by sketching the shape of the returned dossier, especially how four heterogeneous data sections are organized and keyed by domain. It lists the sections, which is partial compensation, but an agent still cannot anticipate the response structure. Pricing is the one piece of completeness it handles well.

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 with 100% schema description coverage ('Target company domains'), so the schema already carries the semantics and baseline 3 applies. The description adds no detail beyond the schema — no note on accepted formats (bare domain vs. URL vs. subdomain), array size limits, or whether results are keyed per domain for batch input.

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 names a concrete verb ('Generate') and a concrete artifact ('360-degree B2B company intelligence dossier') and enumerates its contents: executive contacts, DNS/security posture, ad spend pixels, tech stack. That is far more specific than the title restated. It stops short of a 5 because it never distinguishes itself from siblings that cover a subset of the same ground (enrich_b2b_company_domain, detect_ad_spend_pixels).

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?

Use is only implied by the word 'complete' — the agent can infer this is the all-in-one option versus running individual enrichment and pixel-detection tools, but the description never says so. There are no stated exclusions, prerequisites, or conditions under which a narrower sibling is preferable.

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