SecLens.ONE Email Security

Get Public Corpus Summary

get_summary

Read-onlyIdempotent

Return totals for every domain in the public SecLens.ONE corpus, plus a list of those domains with their latest score, newest first. "stats" holds the domain count, average score, score bands and per-protocol present and effective counts. "results" holds one row per domain (Domain, Score, Generated, Profile, IsMailEnabled, HasNullMX, NullMXCompliant). Use this for overall adoption figures, not for one domain's details (use get_result instead). By default, results lists the 50 newest domains and is about 8 KB. The maximum limit is 500. Stats always cover the full corpus. Set stats_only to true for stats and an empty results list.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_summary"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Newest rows to return. Defaults to 50. Maximum 500. Stats always cover the full corpus.
`stats_only`	No	When true, results is an empty list. Stats still cover the full corpus.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 9, 2026

addedInput schema / properties / limit

Added value: +{
+  "default": 50,
+  "description": "Newest rows to return. Defaults to 50. Maximum 500. Stats always cover the full corpus.",
+  "maximum": 500,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / stats_only

Added value: +{
+  "default": false,
+  "description": "When true, results is an empty list. Stats still cover the full corpus.",
+  "type": "boolean"
+}

First observedOct 29, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive operation, and the description adds substantial behavior beyond that. It explains the stats and results structure, default result size, approximate response size, maximum limit, and that stats always cover the full corpus regardless of limit.

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 front-loaded with what the tool returns and is organized around stats, results, and usage guidance. The field list is justified because there is no output schema, and no sentence is gratuitous.

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 adequately explains both response sections and the fields in each result row. Given the simple two-parameter surface and the existing annotations, an agent has everything needed to call this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents both parameters. The description mostly mirrors that, but it adds useful meaning by noting that the default 50-row response is about 8 KB and by reinforcing that stats are corpus-wide even when results are limited.

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 states a specific verb and resource: it returns totals for every domain in the public SecLens.ONE corpus plus a newest-first domain list. It also distinguishes this tool from get_result by saying this is for overall adoption figures rather than one domain's details.

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 explicitly says when to use this tool (overall adoption figures) and when to use an alternative instead (get_result for one domain's details). The condition is concrete and leaves little inference to the agent.

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 tools Inspect

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.