Skip to main content
Glama

Check TLS certificate expiry for up to 10 hosts

ssl
Read-only

TLS certificate expiry for up to 10 hostnames: the issuer, validity dates, days left, all DNS names and a status (ok, expiring within 14 days, expired, none found). Read from Certificate Transparency logs (CertSpotter, crt.sh as fallback), so it is the newest valid certificate issued for each name, not the one the server presents; the answer also says whether https answers and its HSTS header. Public hostnames only. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "hosts": "<hosts>"
    },
    "name": "ssl"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostsYesComma-separated public hostnames, 1 to 10, e.g. github.com,example.com

Output Schema

NameRequiredDescriptionDefault
noteNo
basisNo
countNo
sourceNo
resultsNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, and the description adds substantial behavior beyond them: the data source (CertSpotter with crt.sh fallback), the critical caveat that the cert shown is the newest issued one rather than the server-presented one, the HTTPS/HSTS side output, the public-hostname restriction, and billing semantics including that failed calls are not charged. That is well above the annotation bar; only the absence of explicit rate-limit or redirect/failure-mode detail keeps it from a 5.

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 resource, host cap, and the returned fields, then the source/caveat, then pricing. Dense but each clause carries information; the pricing/payment sentence is long though it is genuinely decision-relevant for an agent calling a paid tool.

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?

An output schema exists, so return fields need not be re-explained, yet the description still summarizes the key ones and flags the CT-log caveat that would otherwise mislead an agent interpreting the result. With read-only/open-world annotations covering safety and pricing disclosed for a paid endpoint, nothing essential to correct invocation 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?

With a single parameter at 100% schema coverage the baseline is 3, and the description adds real meaning: 'public hostnames only' narrows the accepted input and the '1 to 10' limit reinforces the schema's array bounds. It does not add syntax detail beyond the schema's comma-separated example, so it sits modestly above baseline.

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?

Specific verb+resource with scope ('TLS certificate expiry for up to 10 hostnames') and it enumerates exactly what is returned (issuer, validity dates, days left, DNS names, status). It even distinguishes itself from a naive server-cert check by noting it reads Certificate Transparency logs. It stops short of naming a sibling like 'certs' as the alternative, so it falls just below a 5.

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

Usage Guidelines3/5

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

Usage context is implied rather than stated: the CT-log note tells an agent this is for issued certificates rather than live handshake certs, and 'Public hostnames only' plus the 1-10 cap set boundaries. However, there is no explicit when-to-use/when-not-to-use clause and no named alternative tool to route to when the request falls outside those bounds.

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.

Resources