Skip to main content
Glama

SPF, DMARC, MX & Disposable Domain Security Grader MCP

Bulk Grade Outbound Corporate Domains ($0.01 USDC via x402)

bulk_grade_outbound_domains_x402
Read-onlyIdempotent

Audits up to 12 corporate domains in parallel for MX, SPF, DMARC, DKIM, MTA-STS, and RDAP age. $0.01 a call, paid with x402 (USDC on Base eip155:8453).

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": {
      "domains": "<domains>"
    },
    "name": "bulk_grade_outbound_domains_x402"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainsYesUp to 12 corporate domains to audit in parallel

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 establish readOnly, idempotent, open-world, non-destructive behavior, but they say nothing about cost or payment. The description adds the crucial behavioral detail that each call costs $0.01 in USDC via x402 on Base (eip155:8453), which an agent must know before invoking. It still omits error handling for individual domains that fail validation.

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?

Two tight sentences: the first front-loads what the tool does and what it checks, the second carries the payment prerequisite. No filler, no repetition of the input schema.

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

Completeness3/5

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

There is no output schema, so the description should convey what comes back; it list the checks but not the return shape (per-domain grades, per-check results). For a paid, open-world batch tool, the lack of any failure or partial-result guidance leaves a real gap.

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?

There is a single parameter with 100% schema coverage, so the schema already carries the semantics (array of domain strings, up to 12). The description's 'up to 12 corporate domains to audit in parallel' adds the 'corporate' qualifier and parallel-execution hint but no format or validation details beyond 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/grades) and resource (corporate domains) and enumerates the checks performed: MX, SPF, DMARC, DKIM, MTA-STS, and RDAP age. It does not explicitly distinguish itself from the sibling grade_domain_email_security (presumably single-domain), so bulk-vs-single differentiation is left to the word 'bulk' and 'up to 12'.

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: 'up to 12 domains in parallel' hints at the bulk use case, and a single-domain sibling exists, but the description never states when to pick this tool over that one or what happens with more than 12 domains. No exclusions or prerequisites beyond payment are given.

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.