DataWorks MCP Server

CreateWorkflowDefinition

Define and create data development workflows in DataWorks to automate data processing tasks using FlowSpec specifications.

Instructions

创建数据开发工作流

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": {
      "Spec": "<Spec>"
    },
    "name": "CreateWorkflowDefinition"
  }
}

Input Schema

Name	Required	Description	Default
`ProjectId`	No	DataWorks工作空间的ID
`Spec`	Yes	描述这个工作流的FlowSpec信息

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 18, 2025

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action ('创建') without disclosing behavioral traits. It doesn't mention whether this is a mutating operation, what permissions are required, if it's idempotent, what happens on failure, or what the typical response looks like. For a creation tool with zero annotation coverage, this is a significant gap.

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 a single, efficient sentence with zero wasted words. It's appropriately sized for a simple creation tool and front-loads the essential information.

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

Completeness2/5

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

For a creation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what a successful creation returns, what error conditions might occur, or how this tool relates to other workflow management tools in the system. The 100% schema coverage helps with parameters, but overall context is lacking.

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?

Schema description coverage is 100%, so the schema already documents both parameters (ProjectId and Spec). The description adds no additional meaning about parameter usage, constraints, or relationships beyond what's in the schema. The baseline of 3 is appropriate when the schema does the heavy lifting.

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

Purpose3/5

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

The description '创建数据开发工作流' (Create data development workflow) states the verb and resource but is vague about what constitutes a 'data development workflow' in this context. It doesn't distinguish from siblings like CreateWorkflowInstances or CreateDIJob, leaving ambiguity about the specific type of workflow being created.

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?

No guidance is provided on when to use this tool versus alternatives like CreateWorkflowInstances or CreateDIJob. The description offers no context about prerequisites, dependencies, or appropriate scenarios for creating a workflow definition versus other workflow-related tools in the sibling list.

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

Deploy Server