Skip to main content
Glama

Lookproof DNS, mail and TLS security checks

DKIM selector finder

dkim_discover
Read-onlyIdempotent

Use when the user asks whether a domain has DKIM but no selector is known. Tries 31 common selectors and returns each key found with type, size and flags. None found is a hint, not proof that DKIM is missing. Ex: 'Does example.com use DKIM?'. 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>"
    },
    "name": "dkim_discover"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesA public domain name, e.g. example.com.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, open-world, non-destructive, so the description's job is supplemental — and it delivers: the fixed probe set of 31 selectors, the fields returned per key, the critical caveat that a negative result is a hint rather than proof, and a rate-limit mention for keyless use. The negative-result semantics are exactly the kind of context annotations cannot express.

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?

Front-loaded with the usage condition, then probe behavior, then the caveat, then an example and rate-limit note. Every sentence carries distinct information and none restates the name or schema.

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 one-parameter read tool with fully covered schema and rich annotations, the definition supplies what is missing elsewhere: expected return fields (type, size, flags), interpretation guidance for empty results, and a rate-limit constraint. Nothing an agent needs to call it or interpret output is absent.

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 the single 'domain' parameter is fully documented, so the baseline is 3. The description adds only an inline example domain and the implicit fact that no selector argument exists, which is modest value beyond the schema.

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?

Names a specific action and resource — discovering DKIM selectors by trying common candidates — and scopes it to the case where no selector is known, which implicitly separates it from a selector-based DKIM query. An agent can tell what it does and when it applies without opening the schema.

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 opening clause gives an explicit triggering condition ('no selector is known'), which is a genuine when-to-use rule and implies the when-not case. It also includes a concrete user-phrasing example. It stops short of naming the alternative tool to use when a selector is already known.

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.