Skip to main content
Glama
Sign In
mcp-1panel-plus

mcp-1panel-plus

by EC061
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List SSL Certificates

list_ssls
Read-only

Lists SSL certificates on a selected 1Panel node while excluding private keys and PEM certificate contents.

Instructions

List SSL certificates on the selected node. Private keys and PEM certificate contents are strictly excluded.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_ssls"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-indexed page number.
nodeIdNoTarget node ID: "local" for the Main Node, or a numeric string ID (e.g. "3") from list_nodes.local
page_sizeNoItems per page (1-500).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real value beyond that by stating that private keys and PEM contents are excluded from results, which tells the agent what sensitive material it will not receive. It does not mention pagination defaults or result shape, which keeps it from a 5.

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, both load-bearing: the first states the operation and scope, the second states the exclusion. The scope and the most decision-relevant fact are front-loaded with no filler.

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 must convey what comes back, and it does so partially by clarifying that certificate contents and keys are omitted. For a zero-required-parameter list tool with fully documented schema parameters, this is nearly sufficient, though it leaves the per-certificate fields unstated.

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%, with page, page_size and nodeId all documented in the schema, including the 'local' vs numeric-ID pattern. The description's 'selected node' phrase reinforces nodeId but adds no syntax or constraint 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource ('List SSL certificates') and scopes it to 'the selected node', which distinguishes it from create_ssl and get_ssl_metadata by name alone. It stops short of explicitly naming a sibling to contrast with, so it is clear but not maximally differentiating.

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 explicit when-to-use or when-not-to-use guidance and no mention of the alternative get_ssl_metadata for per-certificate detail. The phrase 'on the selected node' only loosely implies that nodeId should be supplied; an agent must infer the usage context.

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