Skip to main content
Glama

Check TLS/SSL

check_ssl
Read-onlyIdempotent

Attempt an HTTPS HEAD request to a hostname and report whether the TLS handshake succeeded (trusted chain, matching name) with response time.

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": {
      "hostname": "<hostname>"
    },
    "name": "check_ssl"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostnameYesBare hostname, e.g. example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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, lowering the bar. The description adds genuinely useful mechanics beyond that: a HEAD request over HTTPS, the two conditions that count as success (trusted chain, matching name), and the reported response time. It stops short of describing failure/timeout behavior.

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?

One well-formed sentence with the action, the method, the success criteria, and the return value front-loaded. No filler.

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?

For a one-parameter, read-only network check with no output schema, the description covers the mechanics and the core return value. It leaves error modes (DNS failure, connection refused, timeout) unspecified, which is a minor gap.

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 coverage is 100% and the single parameter is documented in the schema as a bare hostname with an example. The description adds no format or syntax meaning beyond that, so the baseline of 3 applies.

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 ('Attempt an HTTPS HEAD request to a hostname') and names the exact success criteria (trusted chain, matching name) plus what is returned (response time). This is clearly distinguishable from siblings like check_url_status or scan_security_headers, which address different concerns.

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?

The description implies the tool's purpose (verifying TLS/certificate validity) but offers no explicit when-to-use versus when-not-to-use guidance and never references alternatives such as check_url_status for plain HTTP status. Usage is inferable but not directed.

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