Skip to main content
Glama

Check a domain's email setup and spoofing protection

email_security
Read-only

Check a domain's email setup and spoofing protection: MX records and email provider (Google Workspace, Microsoft 365, Zoho...), SPF, DMARC policy and common DKIM selectors, with a 0-100 score. Fast (1-3 s). Free: 20 calls/day per user across free tools, no payment needed. Above that: $0.003 per call (x402, USDC on Base).

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": {
      "url": "<url>"
    },
    "name": "email_security"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL
paymentNox402 payment: the base64 PAYMENT-SIGNATURE value signed for the requirements returned by an unpaid call (USDC on Base, gasless). Omit on the first call to get the price and requirements.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Beyond readOnly/openWorld annotations, the description discloses latency (1-3 s), a free quota (20 calls/day across free tools) and the paid path ($0.003/call, x402 USDC on Base). That is exactly the cost/limit context annotations cannot carry, though the payment mechanics largely restate the `payment` schema field.

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 what is checked, then score, then speed and pricing in short clauses. Efficient overall, though the pricing sentence is dense enough to slightly dilute the check list.

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?

For a read-only single-URL check with no output schema, the description covers the covered-information, result shape (0-100 score), latency and cost. The only meaningful gap is the domain-vs-url framing and how the returned findings are structured.

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 the baseline is 3, and the description adds nothing about the two parameters. A mild confusion remains unaddressed: the description speaks of a 'domain' while the required parameter is a `url`, with no explanation of how one maps to the other.

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 a specific verb+resource (check a domain's email setup) and enumerates the exact checks: MX/email provider, SPF, DMARC policy, DKIM selectors, plus a 0-100 score. This clearly separates it from the general-purpose dns and security_headers siblings.

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?

It implies usage through the subject matter (email spoofing protection) and usefully flags speed and cost, but it never says when to pick this over sibling tools like dns or security_headers, nor any prerequisites. Guidance is inferred rather than explicit.

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.