Skip to main content
Glama
Fast Website RAG Markdown Crawler & B2B Contact Finder MCP Server

Fast Website RAG Markdown Crawler & B2B Contact Finder MCP Server

by willowswt

find_company_emails_phones_tech

Read-onlyIdempotent

Extract verified corporate emails, phone numbers, social links, DNS MX deliverability providers, and 50+ B2B technologies from company domains to enrich leads and qualify prospects.

Instructions

Extract verified corporate emails, phone numbers, social links, DNS MX deliverability provider, and 50+ B2B technologies from company domains.

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": {
      "websites": "<websites>"
    },
    "name": "find_company_emails_phones_tech"
  }
}

Input Schema

NameRequiredDescriptionDefault
websitesYesCompany website URLs or domains to enrich.
detectTechStackNoFingerprint 50+ B2B technologies (Shopify, HubSpot, Stripe, etc.).
verifyMxRecordsNoVerify live DNS MX records and email provider.
maxPagesPerDomainNoInternal high-yield pages (/contact, /about, /team) to crawl.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this a safe, idempotent, non-destructive, open-world read, so the bar is lower. The description does add genuine context the annotations lack — results are "verified," MX records are checked live at the DNS level, and 50+ technologies are fingerprinted — but it omits how expensive or slow multi-domain runs are and what a partial/empty result means.

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 with no filler, and the highest-value terms (verified emails, phones, tech stack) are front-loaded. The only weakness is that enumeration of outputs is crammed into one clause rather than structured, making it slightly harder to scan.

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?

With no output schema, the description carries the burden of describing return shape, but only lists fields without saying how they are keyed or what an unverified/missing email looks like. For a multi-domain enrichment tool with an open-world annotation, a note on batching, limits, or result granularity would be expected.

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% and each of the four parameters carries a self-explanatory description (including defaults for detectTechStack, verifyMxRecords, and maxPagesPerDomain). The prose adds nothing beyond that, so baseline 3 is appropriate.

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?

A specific verb ("Extract") paired with a concrete resource list (verified corporate emails, phone numbers, social links, MX provider, B2B technologies) scoped to company domains. It clearly differs in output from the only sibling, a website-to-markdown crawler, though the description never names that alternative to make the contrast explicit.

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?

There is no when-to-use, when-not-to-use, or prerequisite guidance at all — only a statement of what the tool returns. An agent must infer from the required `websites` array that this is a domain-list enrichment tool, and receives no signal about cost, latency, or when the plain crawler would suffice.

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