Skip to main content
Glama
aliyun
by aliyun

UpdateNode

Modify configuration and properties of data development nodes in DataWorks workflows, including execution settings, triggers, and dependencies.

Instructions

更新数据开发节点信息

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ProjectIdNoDataWorks工作空间的ID
IdNo数据开发节点的唯一标识符
SpecYes{ "title": "CycleWorkflow Schema", "description": "定义周期性工作流及其节点配置的JSON Schema", "type": "object", "required": [ "version", "kind", "spec" ], "properties": { "version": { "type": "string", "const": "1.1.0", "description": "Schema版本号,当前固定值1.1.0" }, "kind": { "type": "string", "enum": [ "Workflow", "Node" ], "description": "资源类型,标识工作流的具体类型" }, "spec": { "type": "object", "description": "工作流核心配置规范", "required": [ "nodes" ], "properties": { "nodes": { "type": "array", "description": "工作流节点列表", "items": { "type": "object", "required": [ "name", "script" ], "properties": { "recurrence": { "type": "string", "enum": [ "Normal", "Pause", "Skip", "NoneAuto" ], "description": "节点执行策略:Normal-正常执行, Pause-暂停执行, Skip-跳过执行, NoneAuto-非自动执行" }, "id": { "type": "string", "description": "节点唯一标识符" }, "timeout": { "type": "integer", "minimum": 0, "description": "执行超时时间(单位:秒)" }, "instanceMode": { "type": "string", "enum": [ "T+1", "Immediately" ], "description": "实例生成模式:T+1-次日生成, Immediately-立即生成" }, "rerunMode": { "type": "string", "enum": [ "Allowed", "Denied", "FailureAllowed" ], "description": "重跑策略:Allowed-允许重跑, Denied-禁止重跑, FailureAllowed-失败时允许重跑" }, "rerunTimes": { "type": "integer", "minimum": 0, "description": "最大重跑次数" }, "rerunInterval": { "type": "integer", "minimum": 0, "description": "重跑间隔时间(单位:秒)" }, "datasource": { "type": "object", "description": "数据源配置", "required": [ "name", "type" ], "properties": { "name": { "type": "string", "description": "数据源名称" }, "type": { "type": "string", "enum": [ "odps" ], "description": "数据源类型(当前仅支持odps)" } } }, "script": { "type": "object", "description": "节点执行脚本配置", "required": [ "path", "runtime" ], "properties": { "language": { "type": "string", "description": "脚本语言类型" }, "path": { "type": "string", "description": "脚本存储路径,末尾与节点名称相同,不需要有后缀" }, "runtime": { "type": "object", "description": "运行时环境配置", "required": [ "command" ], "properties": { "command": { "type": "string", "enum": [ "ODPS_SQL" ], "description": "执行命令" }, "cu": { "type": "string", "description": "计算资源单位配置" } } } } }, "trigger": { "type": "object", "description": "节点触发策略配置", "required": [ "type" ], "properties": { "type": { "type": "string", "enum": [ "Scheduler", "Manual", "Streaming", "None" ], "description": "触发类型:Scheduler-定时调度, Manual-手动触发, Streaming-流式触发, None-无触发" }, "cron": { "type": "string", "description": "Cron表达式(仅适用于Scheduler类型)" }, "startTime": { "type": "string", "format": "yyyy-MM-dd hh:mm:ss", "description": "调度开始时间" }, "endTime": { "type": "string", "format": "yyyy-MM-dd hh:mm:ss", "description": "调度结束时间" } } }, "runtimeResource": { "type": "object", "description": "运行时资源配置", "required": [ "resourceGroup" ], "properties": { "resourceGroup": { "type": "string", "description": "资源组名称" } } }, "name": { "type": "string", "description": "节点名称" }, "owner": { "type": "string", "description": "节点负责人" }, "inputs": { "type": "object", "description": "节点输入配置", "properties": { "nodeOutputs": { "type": "array", "description": "输入依赖列表", "items": { "type": "object", "required": [ "data" ], "properties": { "data": { "type": "string", "description": "输入依赖标识" }, "refTableName": { "type": "string", "description": "关联数据表名称(当artifactType为Table时必填)" }, "isDefault": { "type": "boolean", "description": "是否默认输入项" } } } } } }, "outputs": { "type": "object", "description": "节点输入配置", "properties": { "nodeOutputs": { "type": "array", "description": "输入依赖列表", "items": { "type": "object", "required": [ "data" ], "properties": { "data": { "type": "string", "description": "输入依赖标识" }, "refTableName": { "type": "string", "description": "关联数据表名称(当artifactType为Table时必填)" }, "isDefault": { "type": "boolean", "description": "是否默认输入项" } } } } } } } } } } } }}
Behavior1/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but offers none. It doesn't indicate whether this is a mutating operation (implied by 'update' but not explicit), what permissions are required, whether changes are reversible, or what happens on success/failure. For a tool that modifies data development nodes, this lack of behavioral context 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 extremely concise - a single Chinese phrase. While this represents under-specification rather than ideal conciseness, according to the scoring framework, conciseness evaluates whether every sentence earns its place. Here, the single phrase doesn't waste words, so it scores high on this dimension despite being inadequate overall.

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?

Given the tool's complexity (updating nodes with a detailed Spec schema), absence of annotations, and no output schema, the description is completely inadequate. It doesn't explain what 'updating' entails, what fields can be modified, what the response looks like, or any behavioral aspects. For a mutation tool with rich parameter schema but no other structured guidance, this minimal description fails to provide necessary context.

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 all three parameters (ProjectId, Id, Spec) thoroughly. The description adds no additional meaning about parameters beyond what's in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no parameter information in the description.

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 '更新数据开发节点信息' (Update data development node information) is a tautology that essentially restates the tool name 'UpdateNode' in Chinese. It doesn't specify what 'update' means operationally or what aspects of the node are being updated. While it mentions the resource ('data development node'), it lacks a specific verb or scope that distinguishes it from sibling tools like 'UpdateTask' or 'UpdateWorkflowDefinition'.

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

Usage Guidelines1/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing node), exclusions, or compare it to similar tools like 'CreateNode', 'DeleteNode', or 'RenameNode'. The agent receives no contextual cues about appropriate usage scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/aliyun/alibabacloud-dataworks-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server