Skip to main content
Glama

whm_ssl_list

Retrieve a complete list of SSL certificates installed on a WHM server for a given account.

Instructions

List all SSL certificates installed on the server

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountYesAccount alias from accounts.json (use list_accounts to see options)

Implementation Reference

  • src/tools.py:261-268 (registration)
    Registration of the whm_ssl_list tool with its name, description, and input schema (only requires account parameter).
    Tool(
        name="whm_ssl_list",
        description="List all SSL certificates installed on the server",
        inputSchema={
            "type": "object",
            "properties": ACCOUNT_PARAM,
            "required": ["account"]
        }
  • Handler for whm_ssl_list: makes a GET request to the WHM 'fetchsslinfo' JSON API endpoint to retrieve all SSL certificates installed on the server.
    case "whm_ssl_list":
        return await _get(client, url("fetchsslinfo"), headers)
  • Helper function that constructs the WHM JSON API URL for a given function (e.g., 'fetchsslinfo').
    def _whm_url(account: dict, function: str) -> str:
        host = account["host"]
        port = account.get("port", 2087)
        user = account.get("user", "root")
        return f"https://{host}:{port}/json-api/{function}?api.version=1"
  • Generic async HTTP GET helper used by the handler to execute the API call.
    async def _get(client: httpx.AsyncClient, url: str, headers: dict, params: dict = None) -> dict:
        try:
            r = await client.get(url, headers=headers, params=params or {})
            r.raise_for_status()
            return r.json()
        except Exception as e:
            return {"error": str(e)}
  • src/server.py:68-69 (registration)
    The server routes whm_* tool calls to handle_whm_tool, which dispatches to the whm_ssl_list case.
    if name.startswith("whm_"):
        result = await handle_whm_tool(client, account, name, arguments)
Behavior2/5

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

No annotations provided, so description carries full burden. It fails to clarify whether this lists certificates globally or per account, and does not mention read-only nature or any side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence is concise but omits critical scope detail, so it does not fully earn its place.

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

Completeness2/5

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

Lacks specification of output format and scope clarity. With no output schema, more description is needed to be complete for agent usage.

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 already explains the 'account' parameter well. The tool description adds no extra meaning beyond the schema, so baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

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

Description states verb 'List' and resource 'SSL certificates', which is clear. However, it says 'installed on the server' but the required 'account' parameter suggests listing per account, creating ambiguity about scope.

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?

No guidance on when to use this tool versus sibling tools like cpanel_ssl_check. No when-not or alternative context provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/manofsadness/ItchWHMMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server