Skip to main content
Glama
Sign In
aapanel-mcp

aapanel-mcp

by devochkaskustikom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

SSL status of a site

site_get_ssl
Read-onlyIdempotent

Check whether SSL is deployed for a site and return the certificate subject and expiry date when present.

Instructions

Whether SSL is deployed for a site, plus certificate subject and expiry when present.

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": {
      "siteName": "<siteName>"
    },
    "name": "site_get_ssl"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNameYesPrimary domain of the site.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1-alpha.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that certificate subject and expiry are returned 'when present', hinting at conditional/possibly empty results, but says nothing about auth needs, error cases, or response shape.

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?

A single front-loaded sentence that states the resource and the return content with zero redundancy. Nothing to trim.

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 takes on return-value explanation and does so adequately at a high level (deployment status, cert subject, expiry). It is complete enough for a trivial one-parameter read, though it does not characterize the shape of the 'not present' case.

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 there is only one parameter, so the schema fully documents siteName as the primary domain. The description adds no syntax or format detail beyond what the schema already provides; baseline 3 applies.

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?

The description names a specific resource (SSL status of a site) and specifies the returned content: deployment status plus certificate subject and expiry. It is unambiguous against siblings like ssl_deploy or ssl_disable, though it does not explicitly contrast with site_get or ssl_list.

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 call this versus alternatives such as ssl_list or site_get, and no stated prerequisites. The agent must infer usage purely from the tool name.

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