Skip to main content
Glama

Lookproof DNS, mail and TLS security checks

SPF check

spf
Read-onlyIdempotent

Use when the user asks if a domain's SPF record is valid, why a sender fails SPF or if it hits the 10-lookup limit. Returns the include tree, all qualifier and lookup counts. For the IP ranges use spf_flatten. Ex: 'Is the SPF of example.com valid?'. Free trial without an API key: a few calls a day.

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

Input Schema

NameRequiredDescriptionDefault
domainYesA public domain name, e.g. example.com.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, non-destructive, so the description focuses on what annotations cannot say: it discloses the return payload (include tree, qualifier and lookup counts) and a practical constraint (free trial without an API key, a few calls a day). Remaining gaps are minor, e.g. what happens on domains with no SPF record or rate-limit failures.

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 the when-to-use clause, then alternative, then return contents, then a cost caveat -- every sentence carries information. The example question partly restates the first clause but is short enough to earn its place as a trigger phrase.

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?

With no output schema, the description carries the return-value burden and mostly meets it by naming the include tree and lookup/qualifier counts. Slightly more on error or empty-result behavior would make it fully self-sufficient for a diagnostic tool.

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 the schema already documents it at 100% coverage with an example format. The description adds no further constraint beyond what the schema states (e.g. no note on IPs, subdomains, or trailing-dot normalization), 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 and resource -- validating a domain's SPF record -- and enumerates the concrete questions it answers (validity, why a sender fails, whether the 10-lookup limit is hit). It names sibling spf_flatten for the adjacent job, so an agent can distinguish the two without opening a schema.

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?

Explicit when-to-use conditions are given as user-question triggers, plus an explicit alternative ('For the IP ranges use spf_flatten'). The example question further anchors the invocation case.

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.