mcp-1panel-plus

Overview Schema Source Related Servers Discussions Admin

Get Website HTTPS Settings

get_website_https

Read-only

Retrieve HTTPS status, TLS protocols, HSTS, HTTP/3 support, and certificate metadata for a website ID; private keys and PEM contents are excluded.

Instructions

Read HTTPS status, TLS protocols, HSTS, HTTP/3, and certificate metadata for a website ID. Private keys and PEM certificate contents are stripped.

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": {
      "website_id": "<website_id>"
    },
    "name": "get_website_https"
  }
}

Input Schema

Name	Required	Description	Default
`nodeId`	No	Target node ID: "local" for the Main Node, or a numeric string ID (e.g. "3") from list_nodes.	local
`website_id`	Yes	Numeric website ID.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 11, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description still adds genuinely new behavioral context by disclosing that private keys and PEM certificate contents are stripped from the response, telling the agent what data will and will not be present.

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 tight sentences with no filler; the returned-field scope is front-loaded and the redaction caveat follows immediately, so the agent gets both the payload and its limits at a glance.

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 two-parameter read-only tool with full schema coverage and no output schema, the description covers the returned data and its redaction behavior adequately. Minor gap: it says nothing about the nodeId targeting dimension, though the schema documents that parameter fully.

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%, and both parameters (website_id and nodeId) are documented in the schema itself. The description only echoes that a website ID is required and adds no syntax or targeting detail beyond the schema, 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?

The description uses a specific verb ("Read") and an enumerated resource scope: HTTPS status, TLS protocols, HSTS, HTTP/3, and certificate metadata. It is plainly distinguishable from the sibling enable_website_https, which mutates HTTPS rather than reporting on it, without needing to name it.

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 verb "Read" and the requirement of a website ID; there is no explicit statement of when to choose this tool over alternatives such as get_ssl_metadata or get_website, nor any stated prerequisites or exclusions.

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