Skip to main content
Glama

Enterprise B2B Lead, Tech Stack & Regulatory Signal MCP

Qualify B2B Lead & Domain Tech Stack

qualify_b2b_lead
Read-onlyIdempotent

Qualifies a work email or company domain with a 0-100 B2B score using live DNS MX/SPF/DMARC, RDAP domain age, 48 SaaS tech signatures, and ATS open roles.

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": {
      "email_or_domain": "<email_or_domain>"
    },
    "name": "qualify_b2b_lead"
  }
}

Input Schema

NameRequiredDescriptionDefault
email_or_domainYesWork email or corporate domain, e.g. support@cal.com or linear.app

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already establish readOnly, idempotent, openWorld and non-destructive behavior. The description adds useful context that all evidence is fetched live from external sources, implying network latency and dependence on third-party availability, but says nothing about failure behavior for malformed or non-corporate input or about rate limits/cost per call.

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 front-loaded sentence with no filler; each clause contributes a distinct signal. It reads as a dense list rather than a run-on, though slight compression of the signal enumeration would improve scannability.

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 one simple parameter and no output schema, the description carries most of the burden and does say the result is a 0-100 B2B score derived from the listed signals. Still missing: the shape of the rest of the response (does it echo the tech stack and open roles?) and any indication of typical latency.

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 with 100% schema description coverage, and the schema already gives examples for both accepted forms. The description restates 'work email or company domain' without adding constraints such as whether free-mail providers are rejected or whether URLs/schemes are tolerated.

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?

States a specific verb (qualifies) and resource (work email or company domain) and names the concrete signals used (DNS MX/SPF/DMARC, RDAP age, 48 SaaS signatures, ATS roles). That combination cleanly distinguishes it from siblings like list_bulk_b2b_scrapers and extract_ats_hiring_signals.

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: an agent can infer this is for scoring a single lead, but the description never states when to prefer it over a bulk scraper or an ATS-signal extractor. No prerequisites, no input-quality caveats (e.g. free-mail domains), no exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.