Skip to main content
Glama
Sign In

IntoDNS.ai DNS & Email Security Scanner

by ai.intodns
OverviewDiscussionsAdmin

Discover DKIM selectors

discover_dkim
Read-onlyIdempotent

Read-only DKIM check for a domain. Without selector, heuristically queries 50 common selectors and explicitly reports that a miss is inconclusive because DKIM has no enumeration protocol. With selector, performs one authoritative exact lookup for a selector obtained from a DKIM-Signature header or mail provider. Returns discovery method, coverage note, parsed key tags, public-key strength, and warnings. Use exact mode whenever the selector is known; use check_email_security for the broader SPF/DKIM/DMARC overview. No auth or destructive actions.

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

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name only, e.g. example.com (no URL, path, or port)
selectorNoOptional exact DKIM selector, e.g. selector1 or google

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/idempotentHint, so safety is covered; the description adds the non-obvious semantics an agent could not infer: heuristic mode probes 50 common selectors and a miss is documented as inconclusive because DKIM lacks enumeration, while exact mode is one authoritative lookup. It also previews return contents (discovery method, coverage note, key tags, key strength, warnings).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the operation and mode split, and each sentence carries information the agent needs (mode behavior, caveat, return shape, alternative). It is dense to the point of being near the upper limit for a two-parameter tool, but no sentence is 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?

With no output schema, the description still tells the agent what comes back (discovery method, coverage note, parsed key tags, key strength, warnings). Combined with the inconclusive-miss caveat and mode selection rule, nothing needed to invoke or interpret the tool is missing.

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; the description goes beyond it by explaining where a selector value comes from (DKIM-Signature header or mail provider) and how supplying it changes behavior from heuristic to authoritative. It does not add format constraints, but the schema already carries those.

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 ('Read-only DKIM check for a domain') and immediately splits it into two clearly named modes keyed on the `selector` parameter. An agent can distinguish this from check_dmarc or check_email_security without opening any 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 routing rule ('use exact mode whenever the selector is known') and names the alternative tool for the broader job ('use check_email_security for the broader SPF/DKIM/DMARC overview'). Both when-to-use and when-not-to-use are covered.

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

All IntoDNS.ai DNS & Email Security Scanner 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