Skip to main content
Glama

Caelara Labs Compliance & Trust

spf_dmarc_grader

Grade SPF and DMARC DNS records (A-F)

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

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses almost nothing: it does not state that a live DNS lookup occurs, whether results are cached, what happens when records are absent or malformed, or whether the call is read-only. Only the fact that grading happens on an A-F scale is conveyed.

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?

It is one short, front-loaded sentence with no filler, and the resource and output scale both appear immediately. It is, however, terse to the point that nothing else is covered, so it is efficient rather than exemplary.

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 simple single-parameter read tool with no output schema, the description covers the core purpose but leaves meaningful gaps: it never explains what the returned grade consists of (per-record scores, reasons, detected issues) or the failure behavior for domains lacking records. Adequate but incomplete for an agent deciding whether to rely on the output.

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 required parameter at 100% schema description coverage, so the schema already documents 'domain'. The description adds no extra semantics such as accepted formats, subdomain handling, or whether public suffixes are allowed, so baseline 3 applies.

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 ('Grade') and specific resources ('SPF and DMARC DNS records'), plus the output scale (A-F), so it is distinguishable from siblings like security_headers_audit or ssl_cert_inspector. It does not explicitly name a sibling it is not, which keeps it at 4 rather than 5.

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 guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The agent must infer that this applies only to domains with SPF/DMARC records and infer the relationship to the other domain/security tools from the names alone.

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