Skip to main content
Glama

GMPSignal Real-Time Intelligence MCP (59 Tools)

b2b_email_deliverability_dmarc_spf_bimi_auditor

Read-onlyIdempotent

B2B Email Deliverability DMARC/SPF/BIMI Auditor: Audits domain DNS records for DMARC, SPF, DKIM, and BIMI email deliverability compliance.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "b2b_email_deliverability_dmarc_spf_bimi_auditor"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxResultsNoMaximum domain audit results to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / maxResults / description
      Previous value: -"Maximum number of structured items to extract."New value: +"Maximum domain audit results to return."
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -true
  3. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +true
  4. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so safety, repeatability, and external-DNS reach are covered by structured data. The description adds only that the audit targets email deliverability compliance across four record families, which is modest added context. It says nothing about how many domains are audited per call, whether missing records are reported as findings, or how results are bounded.

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 front-loaded sentence with no filler. The only waste is that the label before the colon restates the tool name verbatim, adding no information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an auditor that only accepts a result-count limit, the description is incomplete: it never says which domain(s) get audited or where that target comes from, which is the central thing an agent must know to call it correctly. There is no output schema either, so the description could have usefully sketched what a compliance finding looks like, and it does not.

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% for the single parameter (maxResults, default 10), so the baseline is 3 and the description adds nothing about it. Notably, the description never explains how the target domain is identified, which is the most consequential semantic gap given no domain parameter exists in the schema.

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 specific verb ('Audits') and resource ('domain DNS records') and enumerates the record types checked (DMARC, SPF, DKIM, BIMI), so an agent knows exactly what class of work this performs. It does not differentiate itself from any sibling, but the sibling list is dominated by unrelated lead-gen and scraper tools, so no differentiation is practically needed.

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 guidance, no stated prerequisites, and no mentioned alternative. The one implied usage signal — 'audits domain DNS records' — leaves open whether the domain is supplied by the caller, inferred from context, or configured elsewhere, which is precisely the question an agent needs answered before invoking.

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