Skip to main content
Glama

BRAINIAC Email & Domain Intelligence

Analyze an SPF record

email-domain_spf-record-analyze

Read the published SPF policy and expand redirect or include targets for one level, up to eight lookups. +all is reported as a misconfiguration. Price $0.04 USDC. POST /api/v1/email-domain/spf-record-analyze. Unpaid calls return 402 and do not run.

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": "email-domain_spf-record-analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does notable work: it discloses the one-level expansion limit, the eight-lookup cap, that '+all' is flagged as a misconfiguration, the $0.04 USDC cost, the POST endpoint, and that unpaid calls return 402 without executing. It does not describe what the response body contains, which is the main remaining gap.

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?

Four short sentences, front-loaded with the core action and constraints, with billing/transport details pushed to the end. No filler, though the raw endpoint path is of marginal value to an agent.

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, no-output-schema tool, the description covers scope, limits, failure semantics (402), and cost. The notable gap is return-value shape — an agent cannot tell whether it gets parsed records, lookup counts, or raw TXT strings.

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?

There is one parameter ('domain') with 0% schema description coverage, so the description must compensate. It implies the parameter is the domain whose SPF policy is read, but never states whether it accepts a bare domain vs. subdomain, or whether it must be the owner domain for redirect expansion — a meaningful omission for SPF semantics.

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?

States a specific verb and resource — read the published SPF policy — and adds the key behavior of expanding redirect/include targets one level up to eight lookups. An agent can distinguish this from DMARC/DKIM/MX siblings by the subject matter alone, though no sibling is named.

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 by the SPF-specific framing, but there is no explicit statement of when to choose this over the other email-domain analyzers (e.g. for SPF-specific issues vs. DKIM/DMARC checks). No when-not guidance or prerequisites beyond the payment note.

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