Skip to main content
Glama

check_ssl

Read-onlyIdempotent

Check HTTPS/TLS posture: reachability, HSTS, HTTP-to-HTTPS redirect, and certificate issuer, expiry and SAN count from CT logs (the latest LOGGED certificate, which may differ from the one served).

Instructions

Check HTTPS/TLS posture: reachability, HSTS, HTTP-to-HTTPS redirect, and certificate issuer, expiry and SAN count from CT logs (the latest LOGGED certificate, which may differ from the one served). servedCertificate gives the issuer and expiry of the one actually SERVED on port 443, or not_assessed with a reason. TLS versions and cipher suites are not assessed. Part of the scan_domain audit.

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

Input Schema

NameRequiredDescriptionDefault
domainYesDomain, e.g. example.com
formatNoOutput verbosity.
force_refreshNoBypass the cache.

Output Schema

NameRequiredDescriptionDefault
scoreYes
passedYes
partialNo
categoryYes
findingsYes
checkStatusNo
verdictWithheldNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.111.2
    • changedInput schema / properties / domain / description
      Previous value: -"Domain to check (e.g., example.com)"New value: +"Domain, e.g. example.com"
    • changedInput schema / properties / force_refresh / description
      Previous value: -"Bypass cache and run a fresh check. Useful after DNS changes."New value: +"Bypass the cache."
    • changedInput schema / properties / format / description
      Previous value: -"Output verbosity. Auto-detected if omitted."New value: +"Output verbosity."
  2. Changed1 schema field changedv3.103.1
    • addedInput schema / additionalProperties
      Added value: +false
  3. Changed1 schema field changedv3.98.1
    • addedOutput schema / properties / verdictWithheld
      Added value: +{
      +  "type": "boolean"
      +}
  4. Changed2 schema fields changedv3.54.0
    • addedOutput schema / properties / checkStatus
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / partial
      Added value: +{
      +  "type": "boolean"
      +}
  5. Addedv3.37.0
  6. Removedv3.31.1
  7. First observedv3.29.7

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), and the description adds genuinely non-obvious behaviour: the returned certificate comes from CT logs and may differ from the served one, with a separate servedCertificate field that can be "not_assessed" with a reason. That distinction between logged and served certificates is exactly the kind of nuance an agent cannot get from structured fields.

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?

Three dense sentences, scope first and exclusions after, with no filler or hedging. Every clause conveys coverage or a data-provenance caveat that affects interpretation of results.

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?

Given an output schema exists (so return values need no explanation here), high annotation coverage, and full parameter documentation, the description fills the remaining gaps: scope boundaries, CT-log versus served certificate provenance, and audit-workflow context. Nothing an agent needs in order to call and interpret it is missing.

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?

Schema description coverage is 100%, and the description adds no meaning beyond the schema for domain, format, or force_refresh. Baseline 3 applies: the schema carries the parameter burden entirely.

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?

States a specific verb and resource ("Check HTTPS/TLS posture") and then enumerates exactly what is covered: reachability, HSTS, redirect, certificate issuer/expiry/SAN count from CT logs. It goes further and enumerates what is NOT covered ("TLS versions and cipher suites are not assessed"), which lets an agent separate this from neighbouring HTTP/TLS checks without opening a schema.

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?

Frames the tool's role in the audit workflow ("Part of the scan_domain audit"), which tells an agent when this belongs in a broader sweep versus a standalone call, and the explicit non-coverage statements steer agents away from using it for cipher/version questions. No named alternative is offered for overlapping HTTPS security checks, so it stops short of full when/when-not routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools