Skip to main content
Glama
Sign In

SecLens.ONE Email Security

by one.seclens
OverviewDiscussionsAdmin

Assess Domain Email Security

assess_domain
Idempotent

Start a fresh public email-security check of one domain (SPF, DKIM, DMARC, MTA-STS, TLS-RPT, DANE, DNSSEC, MX and BIMI). Use this when there is no stored result yet or you need an up-to-date one; to read an existing result, call get_result instead. It returns only a queue confirmation, not the report. The response includes poll_after_ms. Wait that long, then poll get_result. A check usually takes a few seconds and is stopped after 45 seconds at most.

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

Input Schema

NameRequiredDescriptionDefault
domainYesRegistrable domain name without scheme, path or port, for example example.com.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / domain / description
      Previous value: -"Domain name, for example example.com"New value: +"Registrable domain name without scheme, path or port, for example example.com."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare the safety profile (readOnlyHint=false, openWorldHint=true, idempotentHint=true, destructiveHint=false); the description adds the crucial asynchronous behavior: it returns only a queue confirmation, not the report, exposes poll_after_ms, typically completes in seconds, and is aborted at 45 seconds. That is exactly the kind of context annotations cannot convey.

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?

Scope comes first, the alternative next, then the return contract and polling sequence in short declarative sentences. There is no filler, and the most decision-relevant information is front-loaded.

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 explains what comes back (a queue confirmation with poll_after_ms) and what to do next, plus the timeout ceiling. For a one-parameter async job starter, an agent has everything needed to call it and handle the result.

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%, and the schema already specifies the registrable-domain format with an example, so the baseline applies. The description reinforces the single-domain scope ('of one domain') but adds no syntax or format detail beyond what the schema provides.

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?

The description opens with a specific verb+resource ('Start a fresh public email-security check of one domain') and enumerates exactly what is inspected (SPF, DKIM, DMARC, MTA-STS, TLS-RPT, DANE, DNSSEC, MX, BIMI). It explicitly contrasts with the sibling get_result, so an agent can route between them without opening either 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?

It gives an explicit when-to-use condition ('no stored result yet or you need an up-to-date one') and names the alternative for the opposite case ('to read an existing result, call get_result instead'). The follow-up sequence (wait poll_after_ms, then poll get_result) is spelled out, leaving nothing to inference.

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

All SecLens.ONE Email Security 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