Skip to main content
Glama
Sign In

SecLens.ONE Email Security

by one.seclens
OverviewDiscussionsAdmin

Get Stored Domain Assessment

get_result
Read-onlyIdempotent

Return the latest stored public report for one domain: score from 0 to 100, profile (mail, null_mx or no_mx), per-protocol findings, and Remediation.packs with the DNS records to publish. BIMI is reported but does not change the score. Use this to read a report or to poll after assess_domain; use get_summary for figures across all domains instead. If the domain has not been checked yet, or the check is still running, it returns HTTP 404 JSON with error not_found. In that case call assess_domain and poll again. Public reports expire after 24 hours.

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

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.6/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered — but the description goes well past them with the 404/not_found error shape, the recovery action, and the 24-hour expiry of public reports. It also preempts a likely misreading by noting BIMI is reported but does not change the score.

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

Conciseness4/5

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

Front-loaded with the return payload, then routing, then failure mode, then expiry — a logical order with no filler sentences. The payload enumeration is dense to the point of being list-like, but every clause carries information an agent needs.

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?

There is no output schema, so the description carries the full burden of telling the agent what comes back, and it does so field by field (score, profile values, per-protocol findings, remediation packs). Combined with the documented 404 behavior and expiry, an agent has everything needed to call this and interpret both success and failure.

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 coverage is 100% and the schema already specifies the format ('Registrable domain name without scheme, path or port, for example example.com'). The description only implies the single-domain scoping ('one domain'), adding no syntax or normalization detail beyond the schema, so the baseline of 3 applies.

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 ('Return the latest stored public report for one domain') and immediately enumerates the payload: score 0-100, profile, per-protocol findings, Remediation.packs. It also names a boundary the sibling does not cover ('get_summary for figures across all domains'), so an agent can distinguish the two 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?

Gives explicit when-to-use cases ('read a report or to poll after assess_domain'), an explicit alternative plus its condition ('use get_summary for figures across all domains instead'), and a failure-mode path ('if the domain has not been checked yet... call assess_domain and poll again'). Nothing about invocation timing is left 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