Skip to main content
Glama
MCP Dokploy Online
by igoruam

schedule-update

Idempotent

Modify an existing Dokploy cron job's expression, command, target, and enabled status to keep automated tasks aligned with current deployment needs.

Instructions

POST /schedule.update

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior2/5

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

Annotations supply openWorldHint and idempotentHint, so some behavioral context exists outside the description. The description itself adds nothing: it does not say whether this is a full replacement or partial update (relevant given 4 required fields out of 17), what happens to omitted fields, or whether it can disable or reassign a schedule.

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?

The single line is short and front-loaded, but it is under-specified rather than concise. It spends its only content restating the endpoint path, which adds no information an agent could act on.

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?

This is a mutation tool with 17 parameters, zero schema descriptions, and no output schema. The description does not compensate for any of that, so an agent has no basis for constructing a valid call beyond the bare JSON schema.

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?

Schema description coverage is 0% across 17 parameters, including two enums (scheduleType, shellType) and a mix of nullable and required fields. The description provides no parameter meaning whatsoever, leaving critical distinctions such as scheduleType selection or shellType behavior entirely undocumented.

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?

The description is only "POST /schedule.update", which essentially restates the tool name and title as an HTTP route. It conveys that a schedule is being updated but says nothing about what is updated or how it differs from siblings like schedule-create 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 Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. An agent must infer from the name alone that this modifies an existing schedule rather than creating, listing, or running one.

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