Skip to main content
Glama

Lookproof DNS, mail and TLS security checks

TLS-RPT check

tlsrpt
Read-onlyIdempotent

Use when the user asks only about TLS-RPT (SMTP TLS reporting). Returns the _smtp._tls record and its report addresses, with findings. For MTA-STS use mta_sts, which includes TLS-RPT. Ex: 'Where do TLS reports for example.com go?'. Free trial without an API key: a few calls a day.

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

Input Schema

NameRequiredDescriptionDefault
domainYesA public domain name, e.g. example.com.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive behavior, so the bar is lower. The description still adds real context the annotations do not: the exact record type inspected, that findings accompany the result, and a rate limit signal ('free trial without an API key: a few calls a day'). What 'findings' contain and how a missing record is reported remain unspecified.

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?

Four short sentences: trigger, output, alternative, example, then the free-tier caveat. Nothing is padded and the disambiguation comes before the example, so the routing decision is front-loaded.

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?

For a one-parameter, non-mutating lookup with no output schema, the description covers when to call it, what comes back, the sibling overlap, and the rate limit. Only the shape of 'findings' and not-found behavior are left implicit, which is minor given annotations and the simple schema.

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?

There is a single required parameter and schema description coverage is 100%, so the schema already defines domain with a length bound and example. The description's example query reinforces the domain concept but adds no new syntax or constraints beyond the structured field, which matches the baseline for full coverage.

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 names a specific protocol (TLS-RPT / SMTP TLS reporting) and states exactly what is returned: the _smtp._tls record, its report addresses, and findings. It also explicitly separates itself from the mta_sts sibling, so an agent can pick 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 trigger (only when the user asks solely about TLS-RPT), names the alternative and the condition that selects it (use mta_sts for MTA-STS, which subsumes TLS-RPT), and reinforces with a concrete example query.

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.