Skip to main content
Glama
Sign In
MCPDactyl

MCPDactyl

by MrMirhan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Run a schedule now

schedule_execute

Trigger a Pterodactyl schedule to run immediately, enabling on-demand execution of scheduled tasks without waiting for the next cron interval.

Instructions

Trigger a schedule to run immediately.

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_execute"
  }
}

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.4/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 behavioral burden. 'Run immediately' does convey that this is a one-off execution rather than a reschedule, but it omits whether the call blocks or returns async, whether it returns run output, whether it requires write permission, and whether the run is recorded in schedule history.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence that is front-loaded, but it is under-specified rather than lean — the brevity comes at the cost of missing behavior and target-resolution detail.

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?

Six parameters, no output schema, no annotations, and an execution-triggering action: the description says nothing about response shape, side effects, or how the two undocumented required parameters resolve. For a mutation/trigger tool this is a substantial gap.

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?

The two required parameters, server and schedule, have no schema descriptions at all, and the description supplies nothing about their format (IDs vs names) or how they identify the target. Only the four optional override parameters are documented in the schema, so the description leaves the critical inputs undefined.

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

Purpose3/5

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

It states a verb-plus-resource (trigger a schedule) and adds the 'immediately' modifier, which distinguishes it from schedule_create/update. But the phrasing is nearly a restatement of the title 'Run a schedule now' and gives no detail on targeting a specific schedule on a specific server.

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?

No guidance on when to use this versus schedule_list/schedule_get (to inspect first) or schedule_task_create, and no prerequisite stated — e.g. that the schedule must already exist and be enabled on the server. The agent must infer whether this causes a one-off manual run or persists anything.

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