Skip to main content
Glama

Lookproof DNS, mail and TLS security checks

MTA-STS and TLS-RPT check

mta_sts
Read-onlyIdempotent

Use when the user asks about MTA-STS or whether inbound mail is protected against TLS downgrade. Returns the record, the fetched policy, mode, max_age and MX coverage, plus the TLS-RPT record. Ex: 'Is MTA-STS set up for example.com?'. 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": "mta_sts"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds what comes back (record, fetched policy, mode, max_age, MX coverage, TLS-RPT record) and notes the free-trial/rate-limit constraint, which is useful context an agent cannot infer elsewhere.

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?

The definition is four short sentences, front-loading the trigger condition, then the return shape, an example, and the rate-limit note. Every sentence carries useful information, though the free-trial note could be trimmed if the agent already has auth context.

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?

There is no output schema, so the description rightly enumerates the returned fields (record, policy, mode, max_age, MX coverage, TLS-RPT). It also states the access constraint, which is enough for an agent to call it correctly for this low-complexity, single-parameter tool.

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?

With one parameter and 100% schema description coverage, the schema already explains the domain argument. The description adds no format or validation detail beyond what the schema provides, so the baseline of 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?

The description states a specific resource (MTA-STS plus TLS-RPT) and a concrete question it answers (TLS downgrade protection), with an example query. It does not differentiate from the sibling 'tlsrpt', yet it also returns the TLS-RPT record, which leaves ambiguity about overlap.

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

Usage Guidelines4/5

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

It gives a clear trigger condition ('Use when the user asks about MTA-STS or whether inbound mail is protected against TLS downgrade') and a sample question. It stops short of naming when-not-to-use or pointing to the tlsrpt sibling for record-only lookups.

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.