Skip to main content
Glama
dolphin-mcp-pilot

dolphin-mcp-pilot

ds_update_schedule_alerts

Add missing FAILURE or ALL alerts to a DolphinScheduler schedule without overwriting existing alert configuration or changing the schedule definition.

Instructions

Add missing alerts only; preserve schedule/definition/task configuration.

Existing FAILURE/ALL with a positive group is skipped, never overwritten. Failures return status=failed with last confirmed state and write receipts; UNKNOWN means a write may have reached DS. Never retry an unknown write. No definition release, workflow run, schedule creation/deletion or rollback.

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>",
      "schedule_id": "<schedule_id>"
    },
    "name": "ds_update_schedule_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
schedule_idYes
project_nameYes
warning_typeNoFAILURE
restore_onlineNo
warning_group_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does so well: it discloses idempotent skip semantics (existing FAILURE/ALL with a positive group is never overwritten), the failure contract (status=failed with last confirmed state and write receipts), and the critical UNKNOWN/never-retry rule for ambiguous writes. It omits permission/auth requirements and any rate-limit or concurrency notes, keeping it below a 5.

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?

Dense, front-loaded, and free of filler: the core constraint ('Add missing alerts only') comes first, followed by skip behavior, failure semantics, and scope exclusions. The telegraphic semicolon phrasing is slightly hard to parse in places but every sentence earns its place.

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

Completeness3/5

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

For a mutation tool with no annotations and no output schema, the description covers write safety and failure semantics thoroughly, but leaves parameter meaning largely unaddressed. An agent could invoke it safely but would be guessing about restore_online and warning_type values.

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 description coverage is 0%, so all five parameters are documented only by titles and defaults. The description gesturing at 'FAILURE/ALL' and 'a positive group' hints at warning_type and warning_group_id semantics, but schedule_id, project_name, restore_online, and the allowed warning_type values are never explained. The compensation is too partial for a 5-parameter tool.

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 operation on a specific resource: add missing alerts to an existing schedule while preserving the schedule/definition/task configuration. The 'add missing only' framing separates it from a blanket overwrite tool, though it never names the sibling read tool (ds_get_schedule_alert_config) it complements.

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?

Provides clear usage context via explicit exclusions: no definition release, no workflow run, no schedule creation/deletion, no rollback. It also implicitly scopes use to filling gaps rather than resetting config. It stops short of naming which alternative tool to use for those excluded operations, so it does not reach a 5.

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