Skip to main content
Glama

Check SPF record

check_spf
Read-onlyIdempotent

Read-only SPF parse and validation for a domain. Recursively walks include/redirect mechanisms to build the full lookup graph, counts DNS lookups against the RFC-7208 10-lookup limit, and returns flattening guidance when the count is close…

Instructions

Read-only SPF parse and validation for a domain. Recursively walks include/redirect mechanisms to build the full lookup graph, counts DNS lookups against the RFC-7208 10-lookup limit, and returns flattening guidance when the count is close to or over the limit. Returns parsed mechanisms, lookup graph, total count, qualifier (~all / -all / +all), and warnings. Use for SPF auditing or before adding new include: senders; use check_email_security for the broader SPF+DKIM+DMARC overview. No auth, no side effects.

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

Input Schema

NameRequiredDescriptionDefault
domainYesDNS name, e.g. example.com, _spf.google.com or _dmarc.example.com (no URL, path, or port)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.11.1
    • changedInput schema / properties / domain / description
      Previous value: -"Domain name only, e.g. example.com (no URL, path, or port)"New value: +"DNS name, e.g. example.com, _spf.google.com or _dmarc.example.com (no URL, path, or port)"
  2. Changed3 schema fields changedv1.10.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / domain / description
      Previous value: -"Domain name, e.g. example.com"New value: +"Domain name only, e.g. example.com (no URL, path, or port)"
    • addedInput schema / properties / domain / maxLength
      Added value: +253
  3. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover readOnly/openWorld/idempotent/non-destructive, and the description goes further: it discloses that the tool performs a recursive DNS walk, that it evaluates the RFC-7208 10-lookup budget, and that it emits flattening guidance near/over the limit — behavior an agent needs to anticipate latency and interpret results. 'No auth, no side effects' reinforces the annotation profile without contradicting it.

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 purpose, then behavior, then usage routing — good ordering. Slight redundancy between the description of the lookup graph/count in the second sentence and the return-value enumeration in the third, but with no output schema the return list still earns its place.

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

Completeness5/5

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

No output schema exists, and the description compensates by naming the returned artifacts (parsed mechanisms, lookup graph, count, qualifier, warnings). Combined with the stated RFC-7208 limit semantics, an agent knows both what it will get back and how to interpret the lookup count.

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 and schema coverage is 100%, so the schema already documents 'domain' fully (including the no-URL/path/port constraint). The description adds nothing about the domain argument beyond what the schema states, which is the baseline expectation here.

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?

Specific verb+resource: 'Read-only SPF parse and validation for a domain', plus the scope of work (recursive include/redirect walk, lookup counting against RFC-7208). It explicitly separates itself from check_email_security, so an agent can distinguish it from the sibling without inspecting schemas.

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

Usage Guidelines5/5

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

States concrete use cases ('SPF auditing or before adding new include: senders') and names the alternative tool with its selecting condition ('use check_email_security for the broader SPF+DKIM+DMARC overview'). The choice between the two is unambiguous.

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