Skip to main content
Glama
Sign In
MCPDactyl

MCPDactyl

by MrMirhan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Add or update a panel

panel_add

Register a Pterodactyl panel by name, base URL, and API keys to store credentials locally; re-adding the same name updates the existing entry.

Instructions

Register a Pterodactyl panel by name with its base URL and API key(s). Persisted locally (chmod 600). Re-adding the same name updates it.

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": {
      "name": "<name>",
      "baseUrl": "<baseUrl>"
    },
    "name": "panel_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
testNoValidate the key(s) against the panel before returning (default true).
baseUrlYes
clientKeyNoClient API key, starts with ptlc_
apiVersionNoPanel API major version: 1 (Pterodactyl 1.x) or 2 (2.0). Default auto detects it.
makeDefaultNo
applicationKeyNoApplication (admin) API key, starts with ptla_

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose meaningful behavior: credentials are persisted locally with chmod 600 and repeated adds are upserts. It omits important mutation semantics — whether omitted keys on update are cleared or preserved, and whether makeDefault changes the active panel.

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?

Three short sentences, front-loaded with the action and followed by the two facts an agent most needs (local persistence, upsert). No filler.

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

Completeness3/5

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

For a 7-parameter, unannotated, no-output-schema mutation tool, the description covers purpose and storage semantics but leaves default-panel behavior and update/overwrite rules unexplained, which is where an agent is most likely to cause unintended credential loss.

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 57%; the description adds the semantic that name is the upsert key and that multiple API keys are accepted, which the schema does not state. However it says nothing about makeDefault or how test/apiVersion interact with the add, leaving the most ambiguous parameters to inference.

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?

Uses a concrete verb and resource ('Register a Pterodactyl panel') and states the identifying inputs (name, base URL, API keys), plus the upsert behavior 'Re-adding the same name updates it.' It does not explicitly contrast with siblings like panel_use or panel_test, so an agent must infer that this is the registration step rather than the selection or validation step.

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

Usage Guidelines3/5

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

The 're-adding the same name updates it' line implies a legitimate update scenario, but there is no explicit when-to-use/when-not guidance and no pointer to panel_use (activate) or panel_test (validate keys). Usage is inferable but not stated.

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