Skip to main content
Glama
Sign In
Keel

Keel

by seayniclabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

check_ssl_cert

Inspect SSL/TLS certificate on any host, returning issuer, subject, expiry date, SANs, and days until expiration.

Instructions

Inspect the SSL/TLS certificate on a host.

Returns issuer, subject, expiry, SANs, and days until expiry.

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

Input Schema

NameRequiredDescriptionDefault
hostYes
portNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations provided, so description bears full burden. Discloses non-destructive inspection and specific returned fields, but lacks details on network dependency, timeout behavior, or handling of invalid certs.

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?

Two concise sentences with clear front-loaded purpose. No unnecessary words or repetition.

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 simple tool with 2 parameters and no output schema, description adequately lists return fields (issuer, subject, expiry, SANs, days). Provides sufficient context for usage.

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 coverage is 0%, no property descriptions. Description only reiterates 'host' implicitly; does not clarify host format (FQDN/IP) or port range. Fails to compensate for missing schema descriptions.

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?

Clearly states the action 'Inspect the SSL/TLS certificate on a host' and lists returned fields. Distinct from sibling tools like http_check or port_check.

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

Usage Guidelines2/5

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

No guidance on when to use this vs. alternatives. Does not mention when not to use (e.g., if only port status needed, use port_check).

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