Skip to main content
Glama

OutboundAuth Deliverability

Check SPF record

check_spf
Read-onlyIdempotent

Look up the live SPF TXT record for a domain and evaluate it: version tag, default policy (-all vs ~all), the 10-DNS-lookup limit, PTR use. Returns a scored verdict with findings.

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
domainYesDomain to check, e.g. example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 the safety profile is covered. The description adds genuine context beyond them: the lookup is against the LIVE record (real-time DNS, results can change) and the output is a scored verdict with findings, not a raw TXT dump.

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?

One dense sentence, front-loaded with the action and target, followed by the evaluated aspects and the return shape. No filler, no repetition of the name or title.

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 single-parameter, read-only, annotation-covered tool with no output schema, this covers what an agent needs: what it does, what it inspects, and that it returns a scored verdict with findings. It falls slightly short by not indicating behavior when no SPF record exists or what a verdict/score range looks like.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

A single required parameter with 100% schema coverage including an example, so the schema already carries the semantics; baseline is high. The description reinforces that the domain is the lookup target for a live record, but adds no format or edge-case detail (e.g. subdomain handling, IDN) beyond the schema.

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 ("look up the live SPF TXT record for a domain") and enumerates exactly what it evaluates: version tag, default policy -all vs ~all, the 10-DNS-lookup limit, PTR use. This is clearly SPF-specific, so it is distinguishable from the DKIM/DMARC/email-auth siblings without opening their schemas.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: an agent can infer this is the tool for SPF inspection on a single domain. There is no explicit when-to-use framing, no mention of how it relates to check_email_auth as an aggregate alternative, and no stated preconditions (e.g. domain must have DNS records).

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