PingDeck Uptime Monitoring

Check an SSL certificate

check_ssl

Read-onlyIdempotent

Get the expiry date of the SSL/TLS certificate of a host and the number of days left. No account and no API key are necessary.

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

Input Schema

Name	Required	Description	Default
`host`	Yes	A host name, for example example.com. A port is optional: example.com:8443.
`api_key`	No	Optional. A PingDeck API key (pd_live_...). Without a key the check uses the free pool: 100 checks a day for each IP address.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive, open-world profile, so the description's added value is the authentication requirement ('no account and no API key') and the shape of the result. Remaining gaps — how failures look for an unreachable host or invalid certificate — are minor for a simple lookup.

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 short sentences, front-loaded with the returned data and followed by the access precondition. No filler, no restatement of the title.

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?

With no output schema, the description usefully states what comes back (expiry date plus days remaining), which is the key thing an agent needs to plan a call. It stops short of covering error/failure semantics for an unreachable host or missing certificate, so it is not fully complete.

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%, including the optional-port syntax and the free-pool quota tied to api_key, so the schema already carries the parameter meaning. The description adds nothing parameter-specific beyond what is documented inline, which is the baseline case.

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?

Names a specific verb and resource ('Get the expiry date of the SSL/TLS certificate of a host') and even states the derived output ('number of days left'), so an agent knows exactly what this does. It does not explicitly contrast with siblings such as check_website or dns_lookup, leaving the distinction to be inferred from the resource name.

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?

Usage is only implied by the purpose: an agent can infer this is the tool for certificate expiry questions. The line 'No account and no API key are necessary' sets a precondition but never states when to prefer an alternative or what conditions make the check inappropriate (e.g., non-HTTPS hosts).

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

All PingDeck Uptime Monitoring tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?