Skip to main content
Glama

List my hosting

list_my_hosting
Read-onlyIdempotent

Returns the list of hosting sites the customer has provisioned, with the control panel (Plesk or CyberPanel) and its URL, setup type (general / WordPress / AI Quick Start), and Plesk login. panelUrl is null when the server has no panel. Use when the user asks "what sites do I have?", "where do I log in to my hosting?", "what's my hosting panel URL?". Read-only.

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_my_hosting"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the description need not prove safety. It goes beyond them by disclosing the return shape and a non-obvious edge case — panelUrl is null when the server has no panel — which prevents an agent from misreading a null as an error. The closing 'Read-only' sentence merely restates annotations, adding no new information.

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

Conciseness4/5

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

Four sentences, front-loaded with the return contract, followed by usage triggers and the null caveat. The trailing 'Read-only.' is redundant with readOnlyHint and could be cut, but the rest is dense and waste-free.

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

Completeness5/5

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

With no parameters and no output schema, the description carries the burden of explaining what comes back, and it does: panel type, URL, setup type, login, plus the null-panel exception. An agent has enough to call it and interpret the result without further context.

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?

The tool takes zero parameters, so the baseline is 4; however, the field descriptions in the text describe the response rather than inputs, and no output schema exists to formalize them. Baseline behavior is adequate with nothing to compensate for.

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 verb and resource ('Returns the list of hosting sites the customer has provisioned') and enumerates the payload fields: control panel (Plesk or CyberPanel), URL, setup type, and Plesk login. It does not explicitly contrast itself with near siblings such as list_my_domains or list_my_backups, but the scope is unambiguous from the field list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete trigger utterances — 'what sites do I have?', 'where do I log in to my hosting?', 'what's my hosting panel URL?' — which map cleanly onto an agent's routing decision. It offers no when-not conditions or named alternatives, so it stops short of full routing guidance, but the positive context is strong.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources