Xserver MCP

List an XServer resource

xserver_list

Read-only

Lists per-server resources: domain, mail, cron, subdomain, ssl, ftp, dns, mail-filter, access-log, error-log. Optionally accepts query parameters.

Instructions

List a per-server resource. Available resources: domain, mail, cron, subdomain, ssl, ftp, dns, mail-filter, access-log, error-log. access-log and error-log require query={ domain }. These paths returned 404 when probed and are not available: php, mysql, mysql-user, wordpress, mail-forward, backup. On an unexpected 404, call xserver_endpoints and then xserver_get with the exact path.

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": {
      "resource": "<resource>"
    },
    "name": "xserver_list"
  }
}

Input Schema

Name	Required	Description
`query`	No	Optional query string parameters, e.g. { limit: "50" }.
`resource`	Yes	Resource key. One of: domain, mail, cron, subdomain, ssl, ftp, dns, mail-filter, access-log, error-log.
`servername`	No	Server name, e.g. xs123456.xsrv.jp. Defaults to the configured/resolved one.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 28, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond annotations (readOnlyHint, openWorldHint), specifies required query parameter for access-log and error-log, documents unavailable paths, and describes error recovery pattern.

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?

Concise, front-loaded with core purpose, then lists resources, special requirements, unavailable paths, and fallback advice. Every sentence is necessary.

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?

Covers purpose, parameter constraints, unavailable resources, and error handling. No output schema, but response structure is implied by 'list' operation. Sufficient for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers all parameters (100%). Description adds value by listing allowed resource values (though not as enum) and clarifying when query is required (for access-log and error-log).

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

Purpose5/5

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

Clearly states it lists per-server resources and enumerates available ones, distinguishing from siblings like xserver_get (which gets by exact path) and xserver_endpoints (which discovers endpoints).

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

Usage Guidelines5/5

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

Explicitly lists available resources and those that are not available (returned 404). Provides alternative guidance: on unexpected 404, call xserver_endpoints then xserver_get.

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

Deploy Server