Skip to main content
Glama

MailX Email Deliverability

by com.themailx
OverviewDiscussionsAdmin

DKIM Check

dkim_check
Read-onlyIdempotent

Use this when the user wants to verify DKIM for a domain. Pass the DKIM selector if known (for example google for Google Workspace, selector1 or selector2 for Microsoft 365). If the selector is unknown, omit it: mailX then tries common selectors and returns the ones it finds. Returns the published key and its status. A miss on common selectors does not prove DKIM is absent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domain_nameYesThe domain to check DKIM records for, e.g. example.com
dkim_selectorNoThe DKIM selector, e.g. google (Google Workspace), selector1 or selector2 (Microsoft 365). Optional: omit it to try common selectors.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / dkim_selector / description
      Previous value: -"The DKIM selector to look up, e.g. google, default, selector1"New value: +"The DKIM selector, e.g. google (Google Workspace), selector1 or selector2 (Microsoft 365). Optional: omit it to try common selectors."
    • changedInput schema / required
      Previous value: -[
-  "domain_name",
-  "dkim_selector"
-]New value: +[
+  "domain_name"
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), so the bar is lower. The description still adds real value: the fallback behavior when the selector is omitted (tries common selectors and returns those found) and the important caveat that a miss does not prove absence.

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?

Five short sentences, front-loaded with the purpose and the key conditional, then the fallback behavior and the caveat. No filler; every sentence carries usable information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 covers the return value ('the published key and its status') and the main limitation of a negative result, which is the critical completeness concern for this tool. Error handling beyond the miss caveat is unstated but not essential.

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 description coverage is 100%, so both parameters are already documented, including the selector examples (google, selector1/selector2) and the omit-to-try-common behavior. The description largely restates what the schema already provides, so baseline 3 is appropriate.

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: 'verify DKIM for a domain.' The resource (DKIM) inherently separates it from siblings like dmarc_check and spf_check, so an agent can route to it 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?

Opens with an explicit when-to-use ('when the user wants to verify DKIM for a domain') and adds conditional guidance for the selector known/unknown cases. It does not explicitly name alternative tools, but the DKIM-specific scope makes the distinction self-evident.

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

All MailX Email Deliverability 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