Skip to main content
Glama

ssl_certificate

Inspect a host's live TLS certificate to verify subject, issuer, SANs, expiry, validity, self-signed status, signature, key details, served chain, health alerts, and negotiated TLS version/cipher.

Instructions

Inspect the live TLS certificate of a host: subject, issuer, SANs, validity.

Returns days until expiry, whether it is currently valid and self-signed, signature algorithm, public-key info and negotiated TLS version/cipher. Includes the served chain (when the Python build exposes it) and health alerts.

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": {
      "host": "<host>"
    },
    "name": "ssl_certificate"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYes
portNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does substantial work: it discloses expiry days, validity, self-signed status, signature algorithm, public-key info, negotiated TLS version/cipher, the served chain, and health alerts. The caveat 'when the Python build exposes it' is a genuinely useful reliability disclosure. It stops short of describing connection failure/timeout behavior, which matters for a network-probing tool.

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 core action and resource, then a compact block of return values. Four sentences, all earning their place, with only minor overlap between 'validity' and the later 'currently valid' restatement.

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?

No output schema and no annotations exist, so the description must describe returns itself — and it does so thoroughly, covering validity, expiry, crypto details, chain, and alerts. The remaining gap is input-side (port handling) and error behavior on unreachable hosts.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for the bare 'host' and 'port' properties, and it does not. 'Of a host' loosely maps to the host parameter, but the port parameter (default 443) is never mentioned, nor is whether a scheme/IPv6/sni form is accepted.

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 opens with a specific verb and resource — 'Inspect the live TLS certificate of a host' — and enumerates the fields returned (subject, issuer, SANs, validity), so the agent knows exactly what the tool produces. It does not explicitly name or contrast with siblings such as crtsh_subdomains or dns_lookup, leaving that differentiation implicit in the word 'live'.

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?

There is no explicit when-to-use or when-not-to-use statement and no named alternative. The adjective 'live' weakly implies this is a direct connection to the host rather than a passive/CT-log lookup, but the agent must infer that distinction on its own.

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