tianshu-mcp

Overview Schema Source Related Servers Discussions Admin

continue_task

continue_task

Resumes tasks paused for user input. Delivers confirmation messages to the original session, reattaches to GUI monitoring, or rechecks login environment and resends task instructions.

Instructions

恢复处于 needs_user 的任务。zcode：agent_question 时 message 发往原会话，关闭旧实例/登录/系统权限场景中 message 仅作已处理确认。codex：user_confirmation 时重新接入观察 GUI 内运行（不发送消息）；login_required 时复检环境后重发任务书。

Input Schema

TableJSON Schema

Name	Required	Description	Default
`taskId`	Yes
`message`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	No
`mode`	No
`model`	No
`round`	No
`checks`	No
`result`	No
`status`	No
`taskId`	No
`agentId`	No
`logFile`	No
`message`	No
`diffstat`	No
`errorType`	No
`finishedAt`	No
`abortSource`	No
`projectPath`	No
`reportFiles`	No
`reportRound`	No
`cancelReason`	No
`changedFiles`	No
`keptInstance`	No
`lastRunSignal`	No
`modelProvider`	No
`needsUserKind`	No
`agentEndReason`	No
`permissionMode`	No
`zcodeSessionId`	No
`pendingQuestion`	No
`progressSummary`	No
`boundProjectPath`	No
`cancelRequestedAt`	No
`verificationSource`	No
`latestVerificationVerdict`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.0.0Sep 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "abortSource": {
+      "type": "string"
+    },
+    "agentEndReason": {
+      "type": "string"
+    },
+    "agentId": {
+      "type": "string"
+    },
+    "boundProjectPath": {
+      "type": "string"
+    },
+    "cancelReason": {
+      "type": "string"
+    },
+    "cancelRequestedAt": {
+      "type": "string"
+    },
+    "changedFiles": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "checks": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "durationMs": {
+            "type": "number"
+          },
+          "name": {
+            "type": "string"
+          },
+          "passed": {
+            "type": "boolean"
+          }
+        },
+        "required": [
+          "name",
+          "passed",
+          "durationMs"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "diffstat": {
+      "type": "string"
+    },
+    "errorType": {
+      "type": "string"
+    },
+    "finishedAt": {
+      "type": "string"
+    },
+    "keptInstance": {
+      "type": "boolean"
+    },
+    "lastRunSignal": {
+      "type": "string"
+    },
+    "latestVerificationVerdict": {
+      "type": "string"
+    },
+    "logFile": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "mode": {
+      "type": "string"
+    },
+    "model": {
+      "type": "string"
+    },
+    "modelProvider": {
+      "type": "string"
+    },
+    "needsUserKind": {
+      "type": "string"
+    },
+    "ok": {
+      "type": "boolean"
+    },
+    "pendingQuestion": {
+      "type": "string"
+    },
+    "permissionMode": {
+      "type": "string"
+    },
+    "progressSummary": {
+      "type": "string"
+    },
+    "projectPath": {
+      "type": "string"
+    },
+    "reportFiles": {
+      "additionalProperties": false,
+      "properties": {
+        "json": {
+          "type": "string"
+        },
+        "md": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "reportRound": {
+      "type": "number"
+    },
+    "result": {},
+    "round": {
+      "type": "number"
+    },
+    "status": {
+      "type": "string"
+    },
+    "taskId": {
+      "type": "string"
+    },
+    "verificationSource": {
+      "type": "string"
+    },
+    "zcodeSessionId": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedv0.5.4Sep 17, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description goes well beyond the sparse annotations, explaining exactly what happens to the message parameter in different scenarios, including cases where no message is sent at all. It also discloses side effects like reconnecting to observe GUI and rechecking the environment, which is valuable behavioral context.

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 compact and front-loads the core purpose, then branches by runtime mode with semicolon-separated cases. Every clause adds behavioral information, with no filler or repetition.

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?

Given the tool's complexity, the description covers the major user-facing states and runtime modes with specific message behavior for each. The output schema exists, so return-value documentation is not required here. The main workflow conditions needed to invoke the tool correctly are all present.

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 description coverage is 0%, so the description must compensate. It does clarify the nuanced behavior of the message parameter across zcode and codex states, which is the critical semantic ambiguity. taskId is less explicitly described, but its meaning is reasonably inferable from the tool's purpose.

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: resumes tasks in the needs_user state. It further distinguishes behavior across zcode and codex modes and specific sub-states, making it clearly distinct from siblings like run_task or cancel_task.

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?

The description clearly scopes usage to tasks in needs_user state and provides situational branches for when each behavior applies. It does not explicitly name alternatives or exclusions, but the context is specific enough that an agent can infer when to call this tool versus run_task.

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

Deploy Server