Skip to main content
Glama

drwho.me

by me.drwho
OverviewDiscussionsAdmin

DKIM lookup

dossier_dkim
Read-only

Probe a domain for DKIM public keys at ._domainkey.. Pass selectors when you know them; omit to probe a built-in list of common selectors used by large mail providers. A selector not on the list will not be found, so an empty result does not prove the domain has no DKIM. Distinguishes a selector that is absent from one that could not be resolved. Parallel Cloudflare DNS-over-HTTPS TXT queries. Returns JSON with a status field: {status:"ok", data, fetchedAt} on success, {status:"not_applicable", reason} when the thing is genuinely absent, {status:"timeout", ms}, or {status:"error", message} when it could not be determined. Treat not_applicable as a finding and error as unknown.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesPublic domain name, e.g. example.com. IP addresses, ports, paths and protocol prefixes are rejected.
selectorsNoDKIM selector names to probe, e.g. ["google", "s1"]. Omit to use the built-in list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / domain / description
      Previous value: -"Public FQDN, e.g. example.com. Must be resolvable on the public internet; IPs, ports, paths, and protocol prefixes are rejected."New value: +"Public domain name, e.g. example.com. IP addresses, ports, paths and protocol prefixes are rejected."
    • changedInput schema / properties / selectors / description
      Previous value: -"DKIM selector names to probe, e.g. [\"google\", \"s1\"]. Omit to probe the built-in common-selectors set: default, google, k1, selector1, selector2, mxvault."New value: +"DKIM selector names to probe, e.g. [\"google\", \"s1\"]. Omit to use the built-in list."
  2. Changed2 schema fields changed
    • changedInput schema / properties / domain / description
      Previous value: -"Public FQDN."New value: +"Public FQDN, e.g. example.com. Must be resolvable on the public internet; IPs, ports, paths, and protocol prefixes are rejected."
    • changedInput schema / properties / selectors / description
      Previous value: -"Optional custom selector list. If omitted, probes the common-selectors set."New value: +"DKIM selector names to probe, e.g. [\"google\", \"s1\"]. Omit to probe the built-in common-selectors set: default, google, k1, selector1, selector2, mxvault."
  3. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint, the description discloses exact status contract, the parallel Cloudflare DNS-over-HTTPS mechanism, and the caveat that empty results are not proof of absence. Treating not_applicable as a finding and error as unknown is exactly the operational nuance an agent needs.

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?

The description is dense but efficient, front-loading the core lookup and then covering selector semantics, result statuses, and interpretation. Every sentence contributes useful guidance with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 fully documents the JSON status variants and their meanings. Combined with schema-covered parameters and safety annotations, nothing critical is missing for invoking this tool correctly.

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 already 100%, but the description adds beyond the schema by explaining the built-in selector list targets large mail providers and that a selector not on the list will not be found. This helps agents decide whether to supply selectors and how to avoid false negatives.

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?

The description uses a specific verb ('Probe') and resource ('DKIM public keys at <selector>._domainkey.<domain>'), which is enough to separate it from generic DNS siblings like dns_lookup and dossier_dns. It also adds a distinctive behavior, distinguishing absent vs unresolved selectors.

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?

The description gives clear context for using the tool, including when to omit selectors and how to interpret an empty result. It does not explicitly name alternatives or when-not-to-use conditions, but the use case is unambiguous enough for an agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All drwho.me toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources