Skip to main content
Glama

Lookproof DNS, mail and TLS security checks

SPF record parser

spf_parse
Read-onlyIdempotent

Use when the user pastes an SPF record to explain or check before publishing. Returns mechanisms, qualifiers, syntax errors and the number of DNS-lookup terms. No DNS lookups; for a live domain use spf. Ex: 'Explain v=spf1 include:_spf.google.com ~all'. 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": {
      "record": "<record>"
    },
    "name": "spf_parse"
  }
}

Input Schema

NameRequiredDescriptionDefault
recordYesThe SPF record as text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, closed-world safety, and the description adds real behavior: it performs no DNS lookups, enumerates the outputs (mechanisms, qualifiers, syntax errors, lookup-term count), and discloses the free-trial/rate-limit ('a few calls a day') constraint.

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?

Four short, front-loaded sentences: trigger, return contents, scope exclusion with alternative, example, then access constraint. No filler or repetition.

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, non-destructive parse tool with no output schema, the description covers inputs, outputs, scope and access limits. Minor gap: it doesn't say whether output is structured or textual, but that is small at this complexity.

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?

Schema coverage is 100% and there is only one parameter, so the schema already carries the meaning of 'record'. The description adds a worked example of what a valid record looks like, which slightly reinforces semantics beyond the single field description.

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 (parse an SPF record) plus exactly what it returns: mechanisms, qualifiers, syntax errors and DNS-lookup term count. It also distinguishes itself from the 'spf' sibling that works on a live domain.

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?

Gives an explicit trigger ('when the user pastes an SPF record to explain or check before publishing') and an explicit exclusion plus the alternative ('No DNS lookups; for a live domain use spf'). It even provides a concrete example utterance.

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.