Skip to main content
Glama

Email security

email_security
Read-onlyIdempotent

Audit domain email authentication: SPF (recursive DNS lookups), DMARC policy, and MX host resolution. $0.002 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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

Input Schema

NameRequiredDescriptionDefault
domainYespublic domain name
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive, so the safety profile is covered. The description adds behavior annotations don't carry: per-call pricing, accepted payment rails, and the two-step terms-then-payment handshake. It stops short of describing result format or failure modes on the second (paid) call.

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?

Three tight sentences: purpose first, then cost, then the call sequence. Pricing and the payment loop are front-loaded where an agent needs them before invoking, with no 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?

For a read-only two-parameter audit with no output schema, the definition covers purpose, cost, and the payment protocol well. Minor gap: it never hints at what the audit returns (pass/fail per record, warnings), which matters because there is no output schema to fall back on.

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 in the schema, and the description largely restates the two-pass payment mechanic. It adds little new meaning about `domain` (no syntax, TLD, or IDN notes) beyond what the schema provides, so 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?

Names a specific verb and resource (audit domain email authentication) and enumerates the three checks performed: SPF recursive lookups, DMARC policy, and MX host resolution. This distinguishes it clearly from siblings like dns_records or security_headers, which are generic DNS/header lookups rather than email-auth auditing.

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

Usage Guidelines4/5

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

Gives explicit invocation guidance for the paid flow: call once without `payment` to get terms, sign with your own wallet, call again with `payment`. It does not, however, say when to choose this over dns_records or email_verify_bulk, so alternative selection is left to inference.

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