Skip to main content
Glama

Lookproof DNS, mail and TLS security checks

DKIM record check

dkim
Read-onlyIdempotent

Use when the user asks whether the DKIM key for a known selector is published and valid. Returns key type, size, testing and revoked flags with findings. Unknown selector: use dkim_discover. Ex: 'Check DKIM selector1 for example.com'. Free trial without an API key: a few calls a day.

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

Input Schema

NameRequiredDescriptionDefault
domainYesA public domain name, e.g. example.com.
selectorYesThe DKIM selector, e.g. selector1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so safety is covered. The description adds value beyond them by disclosing the return payload (key type, size, testing and revoked flags with findings) and a quota constraint (a few calls a day without an API key). It does not say what happens when the record is absent, which keeps it off a 5.

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?

Four short sentences each doing a distinct job: trigger, return content, alternative routing, example, plus a brief availability note. The usage condition is front-loaded and there is no filler.

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?

For a two-parameter read-only checker with no output schema, the description supplies the trigger, the alternative path, the fields returned, and the quota caveat. Nothing an agent needs in order to select and call it correctly is missing.

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 coverage is 100% and both parameters carry their own examples, so the schema does the heavy lifting. The description adds only the implicit expectation that the selector must already be known, without format or syntax detail beyond the schema; baseline 3 applies.

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 action and resource: verifying that a DKIM key for a known selector is published and valid for a domain. It also implicitly separates itself from dkim_discover by scoping to a *known* selector, so an agent can tell the two apart without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit trigger (user asks whether a DKIM key for a known selector is published and valid) and an explicit negative case with the alternative named ('Unknown selector: use dkim_discover'). A concrete example query is included, leaving nothing to inference.

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.