Skip to main content
Glama

Tinplate Edge AI Safety, Security & EU Compliance

tinplate_email_dns

Read-onlyIdempotent

Email DNS Deliverability Auditor API: Audit MX, SPF 10-lookup limits, DMARC, DKIM, and MTA-STS with a 0–100 score. (Endpoint: POST /v1/email-dns)

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

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name or email address to audit (e.g. 'tinplate.dev' or 'hello@tinplate.dev').
recordsNoOptional pre-fetched DNS records for offline auditing without live DNS-over-HTTPS queries.
dkim_selectorsNoOptional custom DKIM selectors to probe in addition to common defaults.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / records / properties / dkim_txt / description
      Added value: +"Pre-fetched DKIM TXT record map keyed by selector name."
    • addedInput schema / properties / records / properties / dmarc_txt / description
      Added value: +"Pre-fetched TXT record values for _dmarc.<domain>."
    • addedInput schema / properties / records / properties / mta_sts_txt / description
      Added value: +"Pre-fetched TXT record values for _mta-sts.<domain>."
    • addedInput schema / properties / records / properties / mx / description
      Added value: +"Pre-fetched MX record values for the domain."
    • addedInput schema / properties / records / properties / txt / description
      Added value: +"Pre-fetched root TXT record values (inspected for v=spf1)."
  2. Changed1 schema field changed
    • addedInput schema / properties / records
      Added value: +{
      +  "description": "Optional pre-fetched DNS records for offline auditing without live DNS-over-HTTPS queries.",
      +  "properties": {
      +    "dkim_txt": {
      +      "additionalProperties": {
      +        "items": {
      +          "maxLength": 2048,
      +          "type": "string"
      +        },
      +        "maxItems": 20,
      +        "type": "array"
      +      },
      +      "type": "object"
      +    },
      +    "dmarc_txt": {
      +      "items": {
      +        "maxLength": 2048,
      +        "type": "string"
      +      },
      +      "maxItems": 20,
      +      "type": "array"
      +    },
      +    "mta_sts_txt": {
      +      "items": {
      +        "maxLength": 2048,
      +        "type": "string"
      +      },
      +      "maxItems": 20,
      +      "type": "array"
      +    },
      +    "mx": {
      +      "items": {
      +        "maxLength": 512,
      +        "type": "string"
      +      },
      +      "maxItems": 50,
      +      "type": "array"
      +    },
      +    "txt": {
      +      "items": {
      +        "maxLength": 2048,
      +        "type": "string"
      +      },
      +      "maxItems": 100,
      +      "type": "array"
      +    }
      +  },
      +  "type": "object"
      +}
  3. Changed10 schema fields changed
    • changedInput schema / properties / dkim_selectors / description
      Previous value: -"Array parameter 'dkim_selectors'"New value: +"Optional custom DKIM selectors to probe in addition to common defaults."
    • addedInput schema / properties / dkim_selectors / example
      Added value: +[
      +  "google",
      +  "selector1",
      +  "default"
      +]
    • addedInput schema / properties / dkim_selectors / items / maxLength
      Added value: +63
    • addedInput schema / properties / dkim_selectors / items / minLength
      Added value: +1
    • addedInput schema / properties / dkim_selectors / maxItems
      Added value: +10
    • changedInput schema / properties / domain / description
      Previous value: -"Parameter 'domain' (e.g. \"cloudflare.com\")"New value: +"Domain name or email address to audit (e.g. 'tinplate.dev' or 'hello@tinplate.dev')."
    • 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
    • changedInput schema / required
      Previous value: -[
      -  "domain",
      -  "dkim_selectors"
      -]New value: +[
      +  "domain"
      +]
  4. First observed

TDQS

B3.2/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 openWorldHint=true, so the safety and external-query profile is covered structurally. The description adds useful behavioral context in the 0–100 score output and the endpoint, but says nothing about authentication needs, rate limits, or latency of the live DNS-over-HTTPS lookups implied by openWorldHint. With annotations carrying the safety profile, this is a moderate value-add rather than a rich disclosure.

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 audited records and the scoring output are front-loaded in a single dense sentence, with the endpoint appended compactly. There is no filler, though the parenthetical endpoint is only marginally useful to an agent selecting the tool.

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?

With no output schema, the description's one-line mention of a 0–100 score does little to describe the report shape (per-record findings, failure reasons, severity). It also omits any mention of the offline pre-fetched-records mode, a notable capability of a 3-parameter tool with a nested object. Adequate but incomplete for a multi-record auditor.

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%, and every parameter including the nested records object and dkim_selectors is documented in the schema itself. The description adds no parameter-level meaning, so the baseline 3 is appropriate.

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 names a specific verb ('Audit') and enumerates the exact resources checked: MX, SPF 10-lookup limits, DMARC, DKIM, and MTA-STS, plus a 0–100 score. An agent immediately knows this is a deliverability inspection tool. It does not explicitly distinguish itself from the sibling tinplate_email_dns_generator, though 'Auditor' vs 'generator' in the names implies the split.

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

Usage Guidelines2/5

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

There is no guidance on when to choose this tool, when to avoid it, or what alternatives exist. Notably absent is any routing advice between live DNS auditing and the optional pre-fetched-records path, which is a meaningful usage decision the agent must make on its own.

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