Skip to main content
Glama

commsharbor

Commsharbor email security check

commsharbor_email_security_check
Read-onlyIdempotent

Check whether someone can send email as a domain: SPF, DKIM in common selectors, DMARC, MX, MTA-STS and BIMI, with a 0-100 score and the fixes, most severe first. Public DNS only. Free, no account. Public DNS only, no account and no charge. The same domain is served from memory for 10 minutes. A network can run 30 new checks per day. DKIM is looked up in common selectors only; dkim_not_found does not prove that no key exists. incomplete: true means a DNS answer failed and the score can be lower than the real one; unread names those parts, and a failed query never becomes a missing finding.

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

Input Schema

NameRequiredDescriptionDefault
domainYesDomain to check, such as example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior5/5

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

Goes well past the readOnly/idempotent/non-destructive annotations: 10-minute in-memory cache for the same domain, a 30-new-checks-per-day-per-network quota, the DKIM common-selector limitation with an explicit warning that dkim_not_found is not proof, and the incomplete/unread semantics with the guarantee that a failed query is never reported as a missing finding. These are exactly the caveats an agent needs to interpret results safely.

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

Conciseness3/5

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

The main purpose is front-loaded and the caveats are dense and load-bearing. But the availability clause is literally duplicated – 'Public DNS only. Free, no account.' and then 'Public DNS only, no account and no charge.' – a wasted sentence that also makes the description read as unedited.

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 carries the return-value burden and does reasonably well: score range, ordering of fixes, and the incomplete/unread fields are all explained. The shape of the findings themselves (per-record status, where the 'fixes' come from) is left implicit, which is the main remaining gap for a tool whose whole value is its report.

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?

One required parameter with 100% schema description coverage ('Domain to check, such as example.com'), so the schema already carries the semantics. The description adds no format constraints (e.g. whether a URL, subdomain, or trailing dot is accepted), so the baseline 3 applies.

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?

Opens with a specific verb and outcome ('check whether someone can send email as a domain') and enumerates exactly what is inspected: SPF, DKIM, DMARC, MX, MTA-STS, BIMI, plus the 0-100 score and severity-ordered fixes. That is far more concrete than the sibling names imply. It does not, however, distinguish itself from the near-identical sibling get_api_x402_email_check, so an agent has no textual signal for which of the two to pick.

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

Usage Guidelines3/5

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

'Public DNS only. Free, no account' establishes prerequisites (no auth, no setup) and the rate limit sets an operational bound. Beyond that, usage is only implied – it never says when to prefer this over get_api_x402_email_check or the domain setup/verify tools, and offers no exclusions.

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.