Skip to main content
Glama

IntoDNS.ai DNS & Email Security Scanner

by ai.intodns

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.

Input Schema

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

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations by explaining the 50-selector heuristic behavior, the inconclusive-miss caveat due to no DKIM enumeration protocol, the exact lookup behavior, and the return contents. Also explicitly states 'No auth or destructive actions,' which extends the annotation context.

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?

Every sentence earns its place. The description is compact, front-loaded, and covers purpose, modes, outputs, alternatives, and safety without 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?

Despite having no output schema, the description lists expected return values (discovery method, coverage note, key tags, strength, warnings). It also clarifies limitations and relationship to siblings, making the tool self-contained for agent decision-making.

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?

The input schema fully documents both parameters with examples. The description adds crucial semantics by explaining how presence/absence of 'selector' changes the tool's behavior and provides source guidance for obtaining an exact selector (DKIM-Signature header or provider).

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?

Opens with 'Read-only DKIM check for a domain' – a specific verb+resource statement. It clearly distinguishes two modes (heuristic multi-selector vs exact single-selector) and differentiates from sibling check_email_security.

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?

Explicitly tells when to use exact mode ('whenever the selector is known') and directs users to check_email_security for a broader overview. It also warns that heuristic-mode misses are inconclusive, guiding appropriate usage.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Every tool has a clearly distinct purpose, and cross-references between tools (e.g., check_spf vs check_email_security vs check_sender_requirements) explicitly state when to use each one. Overlapping behaviors are carefully delineated (e.g., scan_domain vs get_everything_report vs start_deep_scan) with latency and depth tradeoffs explained. No two tools appear to do the same thing.

Naming Consistency4/5

Nearly all tool names follow a verb_noun snake_case pattern (check_*, generate_*, get_*, create_*, scan_*), with precise verbs matching each action. Minor deviations include 'nis2_quickscan' (no verb) and a few compound names like 'whois_lookup', but these are isolated. The variety of verbs is semantically justified by the broad domain, so the naming is predictable and readable.

Tool Count2/5

At 45 tools, this is far beyond the 16-25 'heavy' range and nearly double the 25 threshold. While the server covers a wide range of DNS, email, and web checks, a 45-tool surface is likely to overwhelm agents and increase selection errors. Many tools could be consolidated (e.g., individual check_* tools into one combined check) without sacrificing clarity.

Completeness5/5

The tool set meticulously covers the domain: DNS (SPF, DKIM, DMARC, DNSSEC, propagation, whois), email security (blacklist, FCrDNS, MTA-STS, SMTP TLS, TLSA, BIMI, raw email analysis, test sessions), web security (headers, CSP, HTTP/3), reporting (PDF, snapshots, badges), and compliance (NIS2, Internet.nl deep scans). There are no obvious gaps for the stated purpose of DNS & email security scanning; every check has a corresponding generator or explainer.

Resources