Skip to main content
Glama

ssl_check

Inspect SSL/TLS certificates for a host to verify validity, check expiry, and review issuer, SANs, and cipher details.

Instructions

Inspect the SSL/TLS certificate for a host.

Connects to the host on port 443 and retrieves the full certificate chain.
Returns validity status, expiry countdown (critical for alerting), issuer
details, Subject Alternative Names (SANs), and cipher suite information.

Use to monitor certificate expiry, verify correct certificate installation,
check SANs cover all required subdomains, or audit cipher strength.

Args:
    host: Hostname to check (e.g. 'example.com', 'api.example.com').
          Do not include https:// or path components.

Returns:
    valid (bool): Whether the certificate is currently valid and trusted.
    subject: Common name on the certificate.
    issuer: Certificate Authority that issued it.
    issued_at: Certificate issuance date.
    expires_at: Certificate expiry date.
    days_remaining: Days until expiry (negative = already expired).
    sans: List of Subject Alternative Names (all covered hostnames).
    chain_length: Number of certificates in the chain.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostYes
Behavior5/5

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

With no annotations, the description carries full burden. It fully discloses behavior: connects on port 443, retrieves full chain, and lists all returned fields including validity, expiry countdown, issuer, SANs, and cipher suite info.

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 description is well-structured with a clear intro and bullet points for arguments and returns. It is front-loaded with purpose. While slightly lengthy due to listing all return fields, each sentence earns its place.

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 one parameter, no output schema, and no annotations, the description thoroughly covers purpose, parameter usage, and return values. It provides sufficient detail for an agent to invoke the tool correctly.

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

Parameters5/5

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

The single parameter 'host' has no schema description (0% coverage). The description compensates by providing clear guidance: include only hostname, exclude protocol and path. This adds significant meaning beyond the raw schema.

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 clearly states the tool's function: inspecting SSL/TLS certificates for a host. It specifies connecting to port 443 and retrieving the certificate chain. This distinguishes it from sibling tools like dns_lookup or whois_lookup.

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?

The description provides explicit use cases: monitoring certificate expiry, verifying installation, checking SANs, and auditing cipher strength. However, it does not mention when not to use or alternative tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ForeverTools/kiprio-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server