Skip to main content
Glama
GMPSignal MCP Server

GMPSignal MCP Server

enrich_b2b_company_domain

Read-onlyIdempotent

Turn root company domains into enriched B2B profiles with verified decision-maker contacts, social links, tech stack fingerprints, email security posture, and domain age for prospecting.

Instructions

Enrich B2B company domains with verified decision-maker emails, phone numbers, LinkedIn/X social links, 38+ technology stack fingerprints (CRM, analytics, cloud, payments), MX email provider, SPF/DMARC security posture, and RDAP domain age.

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
domainsYesRoot company domains to enrich (e.g., ["stripe.com", "apify.com"]).
maxResultsNoMaximum number of enriched company profiles to return.
detectTechStackNoWhether to fingerprint 38+ web, cloud, CRM, and payment technologies.
extractContactsNoWhether to extract email addresses, phone numbers, and social profile URLs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.2

TDQS

A3.5/5.0
Behavior3/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 and the description does not contradict it. The description adds real content scope (what categories of data are returned), which matters because there is no output schema. However, it omits behavior an enrichment caller would care about: cost/credit consumption, latency, and what is returned for a domain with no matching contacts or unresolvable DNS.

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?

It is a single sentence with no filler, and the resource ('B2B company domains') is front-loaded before the output list. The long enumerative tail is dense but each item is informative rather than redundant, so it stays readable without wasted 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?

With no output schema, the description usefully enumerates what callers receive, and annotations plus a fully described four-parameter schema cover the rest. The main remaining gap is operational context: result caps per domain, failure behavior for unenrichable domains, and whether the 'verified' emails carry any guarantee. These are secondary for a read-only enrichment call.

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 description coverage is 100%, so all four parameters (domains, maxResults, detectTechStack, extractContacts) are already documented with examples, defaults, and bounds. The description's mentions of '38+ technology stack' and 'emails, phone numbers... social links' loosely correspond to detectTechStack and extractContacts, but add no meaning beyond the schema. Baseline 3 applies.

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 verb 'Enrich' is paired with a precise resource ('B2B company domains') and an explicit inventory of the outputs: decision-maker emails, phones, social links, tech stack, MX, SPF/DMARC, and RDAP age. That makes the tool's function unmistakable. It does not name a sibling or scope boundary, but no sibling in the supplied list overlaps with company enrichment, so confusion risk is low.

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?

Usage is only implied: the enumerated output types signal 'use when you need verified contacts, tech stack, or domain security posture for a company'. There is no explicit when-to-use statement, no when-not-to-use, and no named alternative or prerequisite (e.g., credits, required plan, or what to do if a domain is unknown).

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