Skip to main content
Glama
dolphin-mcp-pilot

dolphin-mcp-pilot

ds_resume_process_instance

Resume a paused workflow instance and continue execution from the point where it was paused in Apache DolphinScheduler.

Instructions

Resume a workflow instance that is in PAUSE state.

Continues from where ds_pause_process_instance stopped it. Not for failed or stopped instances: use ds_rerun_from_failure or ds_rerun_process_instance.

Args: project_name: Project name process_instance_id: Instance ID (from ds_list_process_instances)

Returns: {"process_instance_id": int, "executeType": "RECOVER_SUSPENDED_PROCESS", "status": "submitted"}; the request is asynchronous.

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>",
      "process_instance_id": "<process_instance_id>"
    },
    "name": "ds_resume_process_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_nameYes
process_instance_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.5/5.0
Behavior4/5

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

Given no annotations, the description provides crucial behavioral details such as the asynchronous nature of the request and includes a sample return structure. This allows the agent to correctly anticipate the response lifecycle and content.

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

Conciseness5/5

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

The description is efficient and well-structured. It front-loads the core purpose, followed by critical constraints and external routing advice, without unnecessary filler.

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?

The definition is highly complete for a state-based tool. It covers the specific operational state, handles exceptions by directing the user to other tools, and clarifies the asynchronous execution and response format.

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

Parameters3/5

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

The parameters (project_name, process_instance_id) are straightforward and described within the context of process workflow management. Since the input schema is simple, the description provides adequate context but adds little semantic meaning beyond what the schema defines.

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?

The purpose is stated immediately: to resume a workflow instance specifically in a PAUSE state. It clearly identifies the function and the required state for the operation to be valid.

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

Usage Guidelines5/5

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

It provides precise guidance on when to use the tool (PAUSE state) and explicitly lists alternatives for scenarios where it should not be used (failed or stopped instances). This effectively routes the agent away from incorrect tool usage.

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