Skip to main content
Glama

DNSFix

Check DKIM

check_dkim
Read-onlyIdempotent

Finds a domain's DKIM keys at the usual selector names (or the one you give) and checks key type, length, hash and test mode.

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

Input Schema

NameRequiredDescriptionDefault
domainYesA domain name, for example yourbusiness.com
selectorNoOptional: the DKIM selector, for example google or selector1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 real behavioral context beyond that: it probes 'the usual selector names' by default, meaning multiple DNS lookups may occur, and it enumerates exactly which key properties are validated (type, length, hash, test mode). It does not say what happens when no key is found.

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?

A single sentence with no wasted words; the default-selector behavior is front-loaded and the checked attributes follow compactly. Nothing is repeated from the name or title.

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 should indicate the shape of results, especially since probing multiple selectors could yield multiple per-selector findings or a single aggregated verdict - that ambiguity is left unresolved. It also omits the not-found outcome, which matters for an agent interpreting a diagnostic.

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, but the description genuinely adds meaning the schema lacks: selector is optional because the tool falls back to a set of conventional selector names, which the schema's 'Optional: the DKIM selector' does not convey. It still gives no examples of selector syntax beyond what the schema's examples already provide.

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 a specific verb pair (finds, checks) and resource (DKIM keys), plus the concrete attributes verified: key type, length, hash and test mode. The protocol name inherently separates it from check_spf/check_dmarc siblings, but the description itself never names or contrasts an alternative.

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?

Usage is only implied by the word 'checks' - an agent can infer this is a DKIM diagnostic, but there is no explicit when-to-use, when-not-to-use, or pointer to a sibling such as check_dmarc or lookup_dns for related queries. The parenthetical 'or the one you give' hints at the optional selector case without spelling out the condition.

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