Skip to main content
Glama

Tinplate Edge AI Safety, Security & EU Compliance

tinplate_email_dns_generator

Read-onlyIdempotent

SPF, DKIM & DMARC Record Linter & Generator API: Lint existing SPF/DMARC strings and generate clean, RFC-formatted DNS TXT records. (Endpoint: POST /v1/email-dns-generator)

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": "tinplate_email_dns_generator"
  }
}

Input Schema

NameRequiredDescriptionDefault
ip4NoAuthorized IPv4 addresses or CIDR blocks (`ip4:...`, max 50) for the SPF record.
ip6NoAuthorized IPv6 addresses or CIDR blocks (`ip6:...`, max 50) for the SPF record.
aspfNoSPF alignment mode (`aspf=`): `s` (strict) or `r` (relaxed).s
adkimNoDKIM alignment mode (`adkim=`): `s` (strict) or `r` (relaxed).s
domainYesTarget email domain.
allow_aNoWhen true, includes the domain's `a` mechanism (+1 DNS lookup) in the generated SPF record.
allow_mxNoWhen true, includes the domain's `mx` mechanism (+1 DNS lookup) in the generated SPF record.
dmarc_pctNoPercentage of failing messages (`pct=`, 1–100) subject to the DMARC policy (default 100).
providersNoKnown ESPs whose official SPF includes should be added.
rua_emailsNoAggregate DMARC/TLS-RPT report recipient emails (`rua=mailto:...`, max 10; defaults to `dmarc-reports@<domain>`).
ruf_emailsNoOptional forensic DMARC failure report recipient emails (`ruf=mailto:...`, max 10).
spf_policyNoTerminal SPF policy qualifier: `hardfail` (`-all`), `softfail` (`~all`), or `neutral` (`?all`).hardfail
dmarc_policyNoPrimary DMARC policy (`p=`): `none`, `quarantine`, or `reject`.reject
existing_spfNoOptional existing SPF TXT record to lint for RFC 7208 errors.
existing_dmarcNoOptional existing DMARC TXT record to lint for RFC 7489 errors.
custom_includesNoAdditional custom SPF `include:` domains (max 20; each adds ~2 estimated DNS lookups).
dmarc_subdomain_policyNoOptional DMARC subdomain policy (`sp=`); inherits `dmarc_policy` when omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / adkim / description
      Added value: +"DKIM alignment mode (`adkim=`): `s` (strict) or `r` (relaxed)."
    • addedInput schema / properties / allow_a / description
      Added value: +"When true, includes the domain's `a` mechanism (+1 DNS lookup) in the generated SPF record."
    • addedInput schema / properties / allow_mx / description
      Added value: +"When true, includes the domain's `mx` mechanism (+1 DNS lookup) in the generated SPF record."
    • addedInput schema / properties / aspf / description
      Added value: +"SPF alignment mode (`aspf=`): `s` (strict) or `r` (relaxed)."
    • addedInput schema / properties / custom_includes / description
      Added value: +"Additional custom SPF `include:` domains (max 20; each adds ~2 estimated DNS lookups)."
    • addedInput schema / properties / dmarc_pct / description
      Added value: +"Percentage of failing messages (`pct=`, 1–100) subject to the DMARC policy (default 100)."
    • addedInput schema / properties / dmarc_policy / description
      Added value: +"Primary DMARC policy (`p=`): `none`, `quarantine`, or `reject`."
    • addedInput schema / properties / dmarc_subdomain_policy / description
      Added value: +"Optional DMARC subdomain policy (`sp=`); inherits `dmarc_policy` when omitted."
    • addedInput schema / properties / ip4 / description
      Added value: +"Authorized IPv4 addresses or CIDR blocks (`ip4:...`, max 50) for the SPF record."
    • addedInput schema / properties / ip6 / description
      Added value: +"Authorized IPv6 addresses or CIDR blocks (`ip6:...`, max 50) for the SPF record."
    • addedInput schema / properties / rua_emails / description
      Added value: +"Aggregate DMARC/TLS-RPT report recipient emails (`rua=mailto:...`, max 10; defaults to `dmarc-reports@<domain>`)."
    • addedInput schema / properties / ruf_emails / description
      Added value: +"Optional forensic DMARC failure report recipient emails (`ruf=mailto:...`, max 10)."
    • addedInput schema / properties / spf_policy / description
      Added value: +"Terminal SPF policy qualifier: `hardfail` (`-all`), `softfail` (`~all`), or `neutral` (`?all`)."
  2. Changed31 schema fields changed
    • addedInput schema / properties / adkim
      Added value: +{
      +  "default": "s",
      +  "enum": [
      +    "r",
      +    "s"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / allow_a
      Added value: +{
      +  "default": false,
      +  "type": "boolean"
      +}
    • addedInput schema / properties / allow_mx
      Added value: +{
      +  "default": false,
      +  "type": "boolean"
      +}
    • addedInput schema / properties / aspf
      Added value: +{
      +  "default": "s",
      +  "enum": [
      +    "r",
      +    "s"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / custom_includes
      Added value: +{
      +  "default": [],
      +  "items": {
      +    "type": "string"
      +  },
      +  "maxItems": 20,
      +  "type": "array"
      +}
    • addedInput schema / properties / dmarc_pct
      Added value: +{
      +  "default": 100,
      +  "maximum": 100,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / dmarc_policy / default
      Added value: +"reject"
    • removedInput schema / properties / dmarc_policy / description
      Removed value: -"Parameter 'dmarc_policy' (e.g. \"quarantine\")"
    • addedInput schema / properties / dmarc_policy / enum
      Added value: +[
      +  "none",
      +  "quarantine",
      +  "reject"
      +]
    • addedInput schema / properties / dmarc_policy / example
      Added value: +"reject"
    • removedInput schema / properties / dmarc_rua
      Removed value: -{
      -  "description": "Array parameter 'dmarc_rua'",
      -  "items": {
      -    "type": "string"
      -  },
      -  "type": "array"
      -}
    • addedInput schema / properties / dmarc_subdomain_policy
      Added value: +{
      +  "enum": [
      +    "none",
      +    "quarantine",
      +    "reject"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / domain / description
      Previous value: -"Parameter 'domain' (e.g. \"example.com\")"New value: +"Target email domain."
    • addedInput schema / properties / domain / example
      Added value: +"tinplate.dev"
    • addedInput schema / properties / domain / maxLength
      Added value: +253
    • addedInput schema / properties / domain / minLength
      Added value: +3
    • addedInput schema / properties / existing_dmarc
      Added value: +{
      +  "description": "Optional existing DMARC TXT record to lint for RFC 7489 errors.",
      +  "maxLength": 1024,
      +  "type": "string"
      +}
    • addedInput schema / properties / existing_spf
      Added value: +{
      +  "description": "Optional existing SPF TXT record to lint for RFC 7208 errors.",
      +  "maxLength": 1024,
      +  "type": "string"
      +}
    • addedInput schema / properties / ip4 / default
      Added value: +[]
    • removedInput schema / properties / ip4 / description
      Removed value: -"Array parameter 'ip4'"
    • addedInput schema / properties / ip4 / maxItems
      Added value: +50
    • addedInput schema / properties / ip6
      Added value: +{
      +  "default": [],
      +  "items": {
      +    "type": "string"
      +  },
      +  "maxItems": 50,
      +  "type": "array"
      +}
    • addedInput schema / properties / providers / default
      Added value: +[]
    • changedInput schema / properties / providers / description
      Previous value: -"Array parameter 'providers'"New value: +"Known ESPs whose official SPF includes should be added."
    • addedInput schema / properties / providers / example
      Added value: +[
      +  "google_workspace",
      +  "resend"
      +]
    • addedInput schema / properties / providers / items / enum
      Added value: +[
      +  "google_workspace",
      +  "microsoft_365",
      +  "sendgrid",
      +  "aws_ses",
      +  "mailgun",
      +  "postmark",
      +  "resend",
      +  "hubspot",
      +  "zendesk",
      +  "cloudflare_email"
      +]
    • addedInput schema / properties / rua_emails
      Added value: +{
      +  "default": [],
      +  "example": [
      +    "dmarc-reports@tinplate.dev"
      +  ],
      +  "items": {
      +    "format": "email",
      +    "type": "string"
      +  },
      +  "maxItems": 10,
      +  "type": "array"
      +}
    • addedInput schema / properties / ruf_emails
      Added value: +{
      +  "default": [],
      +  "items": {
      +    "format": "email",
      +    "type": "string"
      +  },
      +  "maxItems": 10,
      +  "type": "array"
      +}
    • removedInput schema / properties / spf_mode
      Removed value: -{
      -  "description": "Parameter 'spf_mode' (e.g. \"hardfail\")",
      -  "type": "string"
      -}
    • addedInput schema / properties / spf_policy
      Added value: +{
      +  "default": "hardfail",
      +  "enum": [
      +    "hardfail",
      +    "softfail",
      +    "neutral"
      +  ],
      +  "example": "hardfail",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "domain",
      -  "providers"
      -]New value: +[
      +  "domain"
      +]
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds only that records are "RFC-formatted" and the POST endpoint path; it says nothing about lookup-count limits, error behavior, or what a lint failure looks like.

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?

Two compact clauses with the core capability front-loaded and the endpoint tucked at the end. Nothing is redundant, though the parenthetical endpoint adds little decision value for an agent.

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 17-parameter tool with no output schema, the description never indicates what is returned — generated TXT records, lint diagnostics, or both. Annotations and the rich schema cover safety and inputs, but the response shape remains entirely undocumented.

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?

Schema description coverage is 100% with enums on five fields, so the schema fully carries parameter meaning (e.g. aspf/adkim, spf_policy qualifiers, DMARC pct). The description adds no syntax or interaction detail beyond what the schema already provides, so the baseline 3 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?

States specific verbs ("lint", "generate") against a specific resource (SPF/DKIM/DMARC DNS TXT records), which lets an agent distinguish this from generic DNS or validation siblings. It does not explicitly contrast with the similarly-named tinplate_email_dns sibling, so the differentiation is only partial.

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?

The description conveys two implied modes — linting existing SPF/DMARC strings and generating new records — but never states when to choose this over tinplate_email_dns or any other sibling, nor any preconditions. Usage must be inferred rather than read.

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