Skip to main content
Glama

Lookproof DNS, mail and TLS security checks

TLS certificate check

tls_certificate
Read-onlyIdempotent

Use when the user asks to check a site's SSL/TLS certificate, why HTTPS fails or when it expires. Returns trust, name match, expiry, issuer, chain, key and TLS version for port 443, with findings. Ex: 'When does the SSL certificate of example.com expire?'. 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": "tls_certificate"
  }
}

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 and non-destructive behavior, so the description's job is to add context beyond that. It does: the check is pinned to port 443, results come back "with findings," and there is a rate-limit disclosure (a few free calls a day). It does not say what happens on an unreachable or invalid domain.

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 most important part — the trigger conditions — is front-loaded, followed by return values and then a usage example. The free-trial line is slightly promotional but still conveys a real quota constraint, so only minor trimming is warranted.

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?

For a one-parameter tool with no output schema, the description supplies everything an agent needs: when to call it, what the input must be, which port is used, and a summary of return fields. Nothing material is missing.

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?

There is a single parameter with 100% schema coverage, so the baseline is 4. The description adds the useful implication that port is fixed at 443 and therefore not a parameter, but it adds no syntax or format detail beyond the schema's "public domain name, e.g. example.com".

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 verb and resource ("check a site's SSL/TLS certificate") and enumerates the returned signals: trust, name match, expiry, issuer, chain, key and TLS version. This clearly separates it from siblings like security_headers or dns_lookup, which do not inspect certificates.

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 explicit trigger conditions — checking a certificate, diagnosing why HTTPS fails, or finding out when it expires — plus a concrete example question. It does not exclude any sibling by name or state when *not* to use it, which keeps it short of a 5.

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.