Skip to main content
Glama

Lookproof DNS, mail and TLS security checks

Mail configuration check

mail_check
Read-onlyIdempotent

Use when the user asks about mail setup or why mail goes to spam (no reputation, content or blocklist checks). Returns MX, SPF, DMARC, DKIM (your selectors) and a spoofing category. One domain per call; domain_health (needs an API key) adds DKIM discovery and MTA-STS. Ex: 'Check example.com'. Free trial without an API key: a few calls a day.

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": "mail_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesA public domain name, e.g. example.com.
dkim_selectorsNoOptional DKIM selectors, comma-separated (at most 5).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), and the description adds real behavioral context beyond that: the scope boundary against reputation/blocklist checks, the per-call domain limit, the API-key prerequisite for the sibling tool, and a rate limit on unauthenticated use.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The trigger condition is front-loaded, followed by return values, scope exclusions, alternatives, and a concrete example — no sentence is filler. The 'Ex: Check example.com' line is short and directly useful.

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

Completeness5/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 compensates by enumerating the returned record types and the spoofing category. Combined with the documented prerequisites and scope limits, an agent has everything needed to decide and call correctly.

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 both parameters are already documented in the schema. The description adds only marginal meaning — reinforcing single-domain scope and implying dkim_selectors are the caller's own selectors — so the baseline 3 applies.

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?

The description names specific records returned (MX, SPF, DMARC, DKIM, spoofing category) and frames it as a single-call aggregate check, which separates it from the individual mx/spf/dmarc/dkim siblings. It also names the deeper alternative, domain_health, without ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the trigger ('user asks about mail setup or why mail goes to spam'), explicitly excludes what it does not do (reputation, content, blocklist checks), and routes to domain_health when API-key-based DKIM discovery and MTA-STS are needed. The 'one domain per call' constraint and free-trial guidance further constrain correct invocation.

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.