Skip to main content
Glama
MCP Dokploy Online
by igoruam

schedule-create

Create cron-based scheduled tasks for applications, Compose services, or servers by defining a name, command, and schedule.

Instructions

POST /schedule.create

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>",
      "cronExpression": "<cronExpression>",
      "command": "<command>"
    },
    "name": "schedule-create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
scriptNo
appNameNo
commandYes
enabledNo
serverIdNo
timezoneNo
composeIdNo
createdAtNo
shellTypeNo
scheduleIdNo
descriptionNo
serviceNameNo
scheduleTypeNo
applicationIdNo
cronExpressionYes
organizationIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

Annotations supply only openWorldHint=true and a title, so the description bears the full burden of behavioral disclosure and supplies none. It does not state that this is a mutating write, that exactly one target field (applicationId/composeId/serverId/serviceName) is likely required, whether it is idempotent, or what permissions are needed.

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

Conciseness2/5

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

It is short, but the brevity is under-specification rather than economy — a bare endpoint path is not front-loaded information an agent can act on. Nothing here is padded, yet almost nothing is said.

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

Completeness1/5

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

A 17-parameter creation tool with no output schema, near-empty annotations, and an enum-driven polymorphic target selection receives a four-word description. An agent cannot construct a correct call from this without inferring everything from field names alone.

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

Parameters1/5

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

With 17 parameters and 0% schema description coverage, the description must compensate and instead adds nothing. Critical semantics are entirely undefined: the meaning of scheduleType's four values, how applicationId vs composeId vs serverId vs serviceName interact with that enum, whether shellType defaults to bash, and what createdAt/scheduleId in the request body imply for the caller.

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

Purpose2/5

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

"POST /schedule.create" merely restates the tool name as an HTTP route; it signals only that something is created and nothing about what a schedule is (cron job, command execution target, service binding). There is no way to distinguish its purpose beyond the name already given, and no differentiation from siblings such as schedule-update or schedule-runManually.

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

Usage Guidelines1/5

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

No guidance at all about when to use this versus schedule-update, schedule-runManually, or schedule-list. No prerequisites, no mention of which of the 17 fields select the scheduling target, and no note on what happens if the schedule already exists.

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