MCPDactyl

List servers

server_list

Lists servers accessible to a client API key on a chosen Pterodactyl panel, enabling filtering by name and scope for owned or admin-managed servers.

Instructions

List servers the client API key can access on the selected panel.

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": "server_list"
  }
}

Input Schema

Name	Required	Description
`page`	No
`type`	No	Scope: owner (default, servers you own), admin (servers you can administer but do not own), admin-all (both). The admin scopes need a key with admin rights.
`uuid`	No
`panel`	No	Name of a saved panel. Omit to use the active or default panel.
`filter`	No	Filter by server name.
`baseUrl`	No	Inline panel URL override, e.g. https://panel.example.com. Not persisted.
`perPage`	No
`clientKey`	No	Inline client API key (ptlc_…) override. Not persisted.
`description`	No
`external_id`	No
`applicationKey`	No	Inline application API key (ptla_…) override. Not persisted.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 25, 2026

TDQS

B3.1/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. 'List' implicitly conveys a read-only operation and the phrase 'the client API key can access' discloses the auth scoping, which is useful context. However, pagination behavior, default page size, and any considerations around the inline, non-persisted credential overrides are left undisclosed.

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?

A single front-loaded sentence with no wasted words; the resource is stated first and the access scope follows. It is efficient, though for an 11-parameter tool one sentence borders on under-specification rather than true conciseness.

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?

With 11 parameters, no annotations, 55% schema coverage, and no output schema, a one-sentence description is not sufficient. Missing are pagination semantics, return shape (e.g., what identifying fields a server entry carries), and any note on how inline panel/clientKey overrides interact with the 'selected panel.'

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 coverage is only 55%, so the description should compensate, but it adds meaning for just two concepts: the client API key (clientKey) and 'the selected panel' (panel, including the default-when-omitted behavior). It says nothing about page/perPage, the filter, or the type scopes, leaving roughly half the parameters undocumented in prose.

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?

States a specific verb and resource ('List servers') plus a meaningful scope: only servers the client API key can access on the selected panel. An agent can infer it is distinct from server_get (single server) and panel_list (panels), but the description never names those siblings to make the distinction explicit.

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 guidance on when to use this versus server_get (single-server fetch) or panel_list (enumerate panels), and no statement of when-not to use it. The only usage hint is the implicit scoping to the 'selected panel,' which the schema already conveys via the panel parameter.

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

Deploy Server