Skip to main content
Glama

DNSFix

Check SPF

check_spf
Read-onlyIdempotent

Reads a domain's SPF record and counts its DNS lookups against the limit of 10, with void lookups, includes and other mistakes in plain words.

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
domainYesA domain name, for example yourbusiness.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds real context beyond that: the 10-lookup threshold it evaluates against, and that findings include void lookups, includes and 'other mistakes' rendered 'in plain words' — i.e. it characterizes the verdict rather than raw DNS output. It stops short of describing behavior on missing/invalid SPF records.

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?

A single sentence with zero filler, front-loaded with the verb and resource and then expanding into what the check yields. Nothing here needs cutting.

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 one-parameter read-only check with no output schema, the description covers purpose, the evaluation threshold, and the shape of the findings. It omits only edge behavior (no SPF record present, malformed domain), a minor gap given the annotations already establish it is a safe idempotent read.

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?

With one parameter at 100% schema description coverage (including a concrete example value), the schema fully carries parameter meaning. The description only implies the input is 'a domain' and adds no format or edge-case detail such as bare-domain vs FQDN handling, so the 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?

States a specific verb+resource ('Reads a domain's SPF record') plus the actual computation performed (counts DNS lookups against the limit of 10) and the findings surfaced (void lookups, includes, other mistakes). This is enough to distinguish it from the DNS-health siblings such as check_dkim and check_dmarc without opening any schema.

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 explicit when-to-use or when-not-to-use guidance, and no sibling is named as an alternative. The only signal is the implied 'you have a domain, you want its SPF health checked' framing, which is inference rather than stated guidance.

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