Skip to main content
Glama

B2b lead audit

b2b_lead_audit
Read-onlyIdempotent

Complete B2B prospect intelligence & technical gap audit for any company domain: crawls contacts & decision-makers, MX-verifies emails, checks DMARC/SPF, TLS, HTTP security headers, and AI-agent readiness (/llms.txt, agent-card, MCP card), returning prioritized pain points and conversion score (0-100). $0.02 per call over x402 or X-API-Key. Not advice.

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": {
      "domain": "<domain>"
    },
    "name": "b2b_lead_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesPublic company domain or website URL (e.g. cloudflare.com)
paymentNoOptional x402 payment header value

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, open-world, idempotent and non-destructive semantics, and the description adds genuinely new context: output shape (prioritized pain points plus a 0-100 conversion score), pricing ($0.02 per call), and the x402/X-API-Key auth paths. It stops short of disclosing crawl limits, latency, or failure behavior on invalid domains.

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?

Front-loaded with the purpose, then capabilities, then cost, then a short disclaimer. The capability list is long but each item earns its place as concrete evidence of scope; only the trailing disclaimer is thin filler.

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 carries the return-value burden and does so by naming the deliverables (pain points, conversion score 0-100). For a multi-check composite tool the only real gaps are crawl scope and error behavior, which are minor at this complexity.

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 coverage is 100%, so both parameters are already documented; baseline is 3. The description reinforces that the domain must be a public company domain or URL and ties the payment parameter to x402/X-API-Key, but it does not explain how an X-API-Key is supplied when the schema only names an x402 header value.

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?

Specific verb-and-resource pairing ('audit' a 'company domain') with an enumerated scope: contacts, MX verification, DMARC/SPF, TLS, headers, AI-agent readiness. It implicitly differentiates itself as a composite bundle versus narrower siblings like security_headers or agent_card_grade, but never names an alternative to make the distinction explicit.

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 by the content ('B2B prospect intelligence' suggests pre-outreach qualification). There is no explicit when-to-use, when-not-to-use, or pointer to narrower sibling tools for single-purpose checks.

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.

Resources