ZapifyAPI MCP Server

check_ssl

Check SSL certificate validity, issuer, and expiry for a domain. Identify expired or invalid certificates to prevent security warnings.

Instructions

Check SSL certificate validity, issuer, and expiry for a domain.

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

Input Schema

Name	Required	Description	Default
`domain`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 3, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states what is checked but does not disclose network dependency, potential timeouts, return format, or error handling. For a tool that likely makes external requests, this is insufficient.

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?

The description is a single, front-loaded sentence with no filler. Every word adds meaning, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter tool, the description minimally conveys what the tool does and what aspects it checks. However, without an output schema or annotations, it lacks details on return value structure, SSL/TLS edge cases, and external network behavior, making it only minimally viable.

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?

The schema lists a single 'domain' parameter with no description. The tool description adds only 'for a domain', which does not clarify expected format (e.g., bare domain vs URL, whether protocols are accepted) or any validation rules. With 0% schema coverage, the description does not compensate adequately.

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 uses a specific verb ('Check') with a clear resource ('SSL certificate') and lists the aspects checked (validity, issuer, expiry). This distinguishes it from sibling tools like dns_lookup and 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 Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives. The description does not mention any exclusions, prerequisites, or contrasting tools that perform similar checks, leaving the agent without context for tool selection.

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