Skip to main content
Glama
Sign In
MCPDactyl

MCPDactyl

by MrMirhan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Delete a schedule

schedule_delete

Delete a schedule and its tasks to clean up unused automated jobs on a Pterodactyl server.

Instructions

Delete a schedule and its tasks.

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>",
      "schedule": "<schedule>"
    },
    "name": "schedule_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
scheduleYes
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

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full burden for a destructive mutation. It usefully discloses that tasks are deleted along with the schedule, but it does not mention irreversibility, confirmation requirements, permissions, or missing-resource behavior.

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?

The definition is a single, front-loaded sentence with no redundant text. It is appropriately sized for its information content, even though more information would be needed for completeness.

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?

For a destructive tool with no annotations, no output schema, and six parameters, the description is too sparse. It leaves required parameters and safety-critical behavior undocumented, so an agent lacks enough context to invoke it responsibly.

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

Parameters2/5

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

Schema coverage is 67%, and critically the two required parameters, server and schedule, are undocumented in the schema. The description only implies that a schedule identifier is needed and adds no meaning for server or the authentication override parameters.

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 states a specific verb and resource: delete a schedule. Adding 'and its tasks' signals a cascade scope that helps distinguish it from schedule_task_delete, though no sibling is named explicitly.

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 guidance on when to use this tool versus alternatives such as schedule_update or schedule_task_delete. The action is inferable from the name, but the description provides no usage context, prerequisites, or exclusions.

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