Skip to main content
Glama

OutboundAuth Deliverability

Check DKIM record

check_dkim
Read-onlyIdempotent

Look up the live DKIM TXT record for a selector (._domainkey.) and evaluate the key: version, key type, public key presence. Follows CNAMEs (e.g. Microsoft 365 / Google selectors).

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>",
      "selector": "<selector>"
    },
    "name": "check_dkim"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain to check, e.g. example.com
selectorYesDKIM selector, e.g. google, selector1, s1 (ask the email provider if unknown)

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, openWorld and non-destructive, so safety is covered. The description adds meaningful behavior beyond them: it follows CNAMEs and names the real-world cases (Microsoft 365 / Google selectors), which an agent could not infer from annotations. It stops short of describing failure modes when no record exists.

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?

Two dense sentences with no filler; the lookup target and the evaluation criteria are front-loaded and each clause carries information.

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 carries the return burden and does so by listing what is evaluated (version, key type, public key presence). It is nearly complete for a read-only diagnostic, missing only how a missing/invalid record is reported.

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%, so the baseline is 3, and the description earns above that by explaining how the two parameters combine into the lookup target ('<selector>._domainkey.<domain>'), which is semantic information the schema does not express.

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 ('Look up the live DKIM TXT record'), plus the exact DNS name format (<selector>._domainkey.<domain>) and what is evaluated. DKIM is inherently distinguishable from the sibling checks (SPF, DMARC, email auth) without ambiguity.

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?

The description says what the tool does but gives no when-to-use, when-not-to-use, or alternative-selection guidance. It does not explain, for example, that this should be run alongside SPF/DMARC checks or what to do when the selector is unknown (that hint lives only in the schema).

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