Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_compliance_spf_dmarc_grader

Grade a domain's SPF and DMARC DNS records on an A–F scale to assess email authentication compliance and identify configuration gaps.

Instructions

[Compliance & Trust] Grade SPF and DMARC DNS records (A-F) Measured p50 12 ms, p95 16 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://compliance.caelaralabs.com.

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

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does supply useful operational context: measured latency (p50 12 ms, p95 16 ms) and the backing endpoint. However, it does not disclose the grading rubric, whether lookups are live DNS queries, failure behavior for domains with no records, or whether results are cached — all relevant for a tool whose whole output is a judgment score.

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?

The definition is two short sentences with the primary purpose front-loaded and no filler. The benchmark citation and endpoint are compact, though the dated benchmark string is borderline noise for an agent choosing a tool.

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?

For a single-parameter grading tool the description covers purpose, latency, and endpoint, and no output schema exists so return values arguably need explanation — but the description never says what comes back beyond an A-F grade (issues found, record contents, remediation hints). Adequate but 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?

Only one parameter exists with 100% schema coverage, so the schema already defines 'domain' adequately and the baseline is 3. The description adds nothing about accepted formats — bare domain vs. URL vs. email address — which is a common source of invocation error for DNS-grading tools.

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?

"Grade SPF and DMARC DNS records (A-F)" gives a concrete verb, a specific resource (SPF/DMARC records), and the output shape (letter grade). It distinguishes itself from sibling audits like security_headers_audit or domain_trust_composite by naming exactly which records are graded, though it does not explicitly state when to prefer the composite trust tool instead.

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 prerequisites (e.g. domain must have DNS published), and no mention of alternatives. An agent must infer from the tool name alone that this is for email-authentication posture rather than general domain trust, and the sibling tools above offer overlapping options with no routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools