Skip to main content
Glama

BRAINIAC Email & Domain Intelligence

Check DKIM records

email-domain_dkim-record-check

Look up DKIM public keys for the supplied selectors. When no selector is supplied, only google, selector1, selector2, s1, s2, and k1 are queried. Price $0.04 USDC. POST /api/v1/email-domain/dkim-record-check. Unpaid calls return 402 and do not run.

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": "email-domain_dkim-record-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes
selectorsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses that the endpoint is paid ($0.04 USDC), uses POST /api/v1/email-domain/dkim-record-check, and returns 402 without running when unpaid, but it omits payment/auth mechanics and broader error or rate-limit behavior.

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?

The description is short and front-loaded, leading with the lookup action before selector defaults, pricing, endpoint, and 402 behavior. Every sentence adds operational or scoping value without filler.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter paid lookup with no annotations and no output schema, the description covers purpose, selector defaults, pricing, endpoint, and unpaid-call behavior. However, it leaves the domain input format, payment/auth flow, and response shape unstated, leaving clear gaps for an agent invoking it.

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 0%, so the description must compensate for both parameters. It explains the optional selectors behavior, including the exact default set used when omitted, but it never defines what 'domain' expects, such as a bare domain versus a full email address, and does not clarify the six-selector maximum.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource: 'Look up DKIM public keys for the supplied selectors.' The DKIM scope makes it distinguishable from siblings like MX, SPF, and DMARC checks, though no sibling is explicitly named or routed against.

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

Usage Guidelines2/5

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

The description provides no explicit when-to-use or when-not-to-use guidance relative to alternatives. It only implies usage by describing DKIM lookup behavior and the default selector set.

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.

Resources