Skip to main content
Glama
Sign In
MCPDactyl

MCPDactyl

by MrMirhan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Assign an allocation

network_assign

Allocate a new IP/port for a Pterodactyl server; if no IP or port is provided, the next available allocation is assigned automatically.

Instructions

Request a new allocation. With no ip/port the next available one is auto-assigned.

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": {
      "server": "<server>"
    },
    "name": "network_assign"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipNo
portNo
panelNoName of a saved panel. Omit to use the active or default panel.
serverYes
baseUrlNoInline panel URL override, e.g. https://panel.example.com. Not persisted.
clientKeyNoInline client API key (ptlc_…) override. Not persisted.
applicationKeyNoInline application API key (ptla_…) override. Not persisted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It implies a mutation but says nothing about required permissions, what happens when the requested ip/port is already taken, whether the allocation is reversible, or what the tool returns. For a write operation with zero annotation coverage this is a meaningful gap.

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?

Two short sentences with the core behavior front-loaded and no filler. It is efficient though arguably too terse for a 7-parameter mutation tool.

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 7 parameters, no annotations, and no output schema, the description should explain return shape, error behavior on conflicting ip/port, and how the panel/override parameters interact. None of that is present, so an agent must infer most of the calling contract.

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%, and the description adds the one piece of semantics the schema lacks: omitting ip/port triggers auto-assignment of the next free allocation. It adds nothing about the server, panel, or inline override parameters (baseUrl/clientKey/applicationKey), leaving those to their schema descriptions.

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 uses a clear verb+resource ('Request a new allocation') that identifies the operation as creating an allocation, which implicitly distinguishes it from siblings like network_list, network_delete, and network_set_primary. However, it never ties the action to the required 'server' scope or explicitly names a sibling, so the differentiation is left to inference.

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?

'With no ip/port the next available one is auto-assigned' gives a genuine usage rule for the optional parameters, which implies when to omit them. But there is no guidance on when to use this versus network_list/network_set_primary, and no prerequisites (panel resolution, permissions) are 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