Skip to main content
Glama
dolphin-mcp-pilot

dolphin-mcp-pilot

ds_set_schedule

Creates an offline cron schedule for a DolphinScheduler workflow using a required Quartz expression; activate it afterwards to run jobs automatically on your defined interval.

Instructions

Create a schedule for a workflow (created OFFLINE; activate with ds_online_schedule).

v2.0.12: cron is now required (no default) to prevent silent misuse.

Args: project_name: Project name workflow_code: Process-definition code cron: Quartz 7-field expression (required, e.g. "0 0 6 * * ? *") start_time: Start time yyyy-MM-dd HH:mm:ss; defaults to today 00:00:00 end_time: End time; defaults to 2030-12-31 23:59:59 warning_type: NONE, SUCCESS, FAILURE (default) or ALL warning_group_id: Alert group ID; positive when alerts are enabled timezone_id: IANA timezone (default Asia/Shanghai)

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": {
      "project_name": "<project_name>",
      "workflow_code": "<workflow_code>",
      "cron": "<cron>"
    },
    "name": "ds_set_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
cronYes
end_timeNo
start_timeNo
timezone_idNoAsia/Shanghai
project_nameYes
warning_typeNoFAILURE
workflow_codeYes
warning_group_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the load and does disclose meaningful behavior: the schedule is created inactive/offline and must be activated separately, and cron is deliberately required in v2.0.12 to prevent silent misuse. It also surfaces the hidden defaults that will silently apply (start today 00:00:00, end 2030-12-31 23:59:59, timezone Asia/Shanghai). It stops short of saying what happens on duplicate schedules or what the call returns (e.g., a schedule ID).

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?

Front-loaded with the behavioral fact that matters most (created OFFLINE), then an efficient Args list where each line carries distinct information. The version-stamped note ("v2.0.12: cron is now required") is slightly noisy but justifies the required change, so it earns its place.

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

Completeness5/5

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

For an 8-parameter mutation tool with no annotations and no output schema, the description covers purpose, activation lifecycle, all parameters with formats and defaults, and the reasoning behind the required cron. An agent has enough to invoke it correctly on the first try without guessing.

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

Parameters4/5

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

Schema coverage is 0%, so the Args block is doing all the work and it delivers formats the schema lacks: Quartz 7-field cron with an example, yyyy-MM-dd HH:mm:ss timestamps, IANA timezone, and the NONE/SUCCESS/FAILURE/ALL enumeration for warning_type. Gaps remain on warning_group_id ("positive when alerts are enabled" is imprecise) and on workflow_code, which the schema types as integer while the description only calls it a "process-definition code."

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

Purpose5/5

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

States a specific verb and resource ("Create a schedule for a workflow") and immediately qualifies the resulting state as OFFLINE, then names the sibling (ds_online_schedule) that makes it live. An agent can distinguish this from ds_update_schedule_cron or ds_online_schedule without reading the schema.

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

Usage Guidelines4/5

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

Clear context for when to use it (initial schedule creation) and an explicit pointer to ds_online_schedule as the follow-up activation step, which is a real exclusion of behavior this tool does not perform. It does not address what to do when a schedule already exists for that workflow (create vs. update), which is the main remaining ambiguity.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.