Skip to main content
Glama

Lookproof DNS, mail and TLS security checks

SPF flattening check

spf_flatten
Read-onlyIdempotent

Use when the user asks which IP addresses or servers may send mail for a domain, or to flatten SPF. Returns every IPv4 and IPv6 block the record authorizes, with the include it came from. Analysis only. Ex: 'Which IPs may send mail as example.com?'. 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_flatten"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the safety bar is low. The description still adds genuine operational context: it is analysis-only (nothing is modified), it returns both address families with include provenance, and there is a free tier limited to a few calls per day absent an API key. That rate-limit/auth disclosure is the most valuable piece, but return shape and any lookup-failure behavior remain unstated.

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?

The description is front-loaded with the usage trigger, then output content, then scope caveat, then example, then access note — a sensible order with little waste. The free-trial sentence earns its place as operational context, though the example slightly duplicates the already-stated purpose.

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 one-parameter read-only analysis tool with no output schema, the definition covers trigger, scope, and roughly what comes back, which is close to sufficient. The gaps are that 'Analysis only' is ambiguous (it could mean no live DNS resolution or no record modification) and the response form is described only loosely, leaving the agent unsure about failure cases or lookup depth.

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 a single parameter at 100% schema coverage, the schema already defines 'domain' with an example and length limit. The description only reinforces that the domain is the SPF subject; it adds no constraint, format, or edge-case guidance beyond the schema, so the baseline 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 states a concrete purpose: returning every IPv4 and IPv6 block an SPF record authorizes, plus the include each block came from, and frames it as both an IP-authorization question and an SPF flattening check. That distinguishes it functionally from parse-style siblings like spf_parse, though no sibling is named explicitly, so the differentiation is inferential rather than stated.

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

Usage Guidelines4/5

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

It gives explicit trigger conditions ('when the user asks which IP addresses or servers may send mail for a domain, or to flatten SPF') plus a concrete example query, and 'Analysis only' narrows scope away from write/mutation tools. It stops short of naming alternatives or saying when another SPF tool would be the better pick.

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.