Skip to main content
Glama

Lookproof DNS, mail and TLS security checks

Email spoofing check

spoofable
Read-onlyIdempotent

Use when the user asks whether someone can send email pretending to be a domain. Returns protected, partial, monitoring, unprotected or broken from the DMARC policy, with gaps. Describes the policy; it does not prove forged mail gets through. Ex: 'Can someone spoof 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": "spoofable"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds value beyond them: it discloses the exact result vocabulary returned and, importantly, a free-trial rate limit ('a few calls a day' without an API key), which affects how an agent should batch or retry calls.

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 trigger condition and then layers output vocabulary, the scope caveat, an example and rate-limit info, with no filler sentences. It is dense but every clause carries information an agent can act on.

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 correctly compensates by enumerating the return values and note that gaps are included. A small residual gap is that 'with gaps' is never defined, so the agent cannot describe the response shape precisely to a user.

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?

There is only one parameter and schema coverage is 100%, so the schema already carries the meaning; the description reinforces it with a worked example ('Can someone spoof example.com?'). No additional format or constraint detail is needed beyond the schema's maxLength and public-domain requirement.

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 gives a concrete verb-plus-resource ('check whether someone can send email pretending to be a domain') and enumerates the possible outputs (protected, partial, monitoring, unprotected, broken), which tells an agent exactly what the tool evaluates. It does not explicitly distinguish itself from siblings like dmarc or dmarc_parse, so an agent must infer that this is the interpretive 'spoofability' verdict rather than a raw record fetch.

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 opens with an explicit trigger ('Use when the user asks whether someone can send email pretending to be a domain') and adds a concrete example query. It also sets a boundary with 'it does not prove forged mail gets through,' which is a genuine when-not caveat, though no sibling alternative is named for the case where raw DMARC records are wanted.

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.