Enable SSL for a website hosted on 1Panel by providing website ID, certificate, private key, and SSL type to activate HTTPS access.
Apply SSL to website
| Name | Required | Description | Default |
|---|---|---|---|
| type | Yes | ||
| enable | Yes | ||
| websiteId | Yes | ||
| httpConfig | No | ||
| privateKey | No | ||
| certificate | No | ||
| websiteSSLId | No |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It only repeats the name and adds 'to website', with no mention of permissions, reversibility, side effects, or what 'enable' does. Score 1.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One short sentence, front-loaded, but severely under-specified for a 7-parameter configuration tool. It is concise only because it omits necessary detail. Score 2.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given 7 parameters, no annotations, no output schema, and many SSL siblings, the description is far too incomplete for an agent to invoke correctly. Score 1.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% and the description mentions none of the 7 parameters (websiteId, type, enable, httpConfig, privateKey, certificate, websiteSSLId). It provides no syntax, allowed values, or meaning for any parameter. Score 1.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a verb 'Apply' and resource 'SSL to website', so the high-level purpose is discernible. However, 'apply' is vague against the many SSL siblings (obtain_ssl, upload_ssl, renew_ssl, update_https) and does not specify whether it creates, binds, or toggles SSL. Score 3.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No indication of when to use this tool versus alternatives like obtain_ssl, upload_ssl, or update_https. No prerequisites or context are given. Score 2.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.