tianshu-mcp

Overview Schema Source Related Servers Discussions Admin

prepare_visual_baseline

prepare_visual_baseline

Prepare visual baseline candidates for review, returning a summary and preview before formal adoption. Requires user authorization.

Instructions

准备视觉基准候选，返回摘要与预览；不采用正式基准。需要用户授权。

Input Schema

TableJSON Schema

Name	Required	Description	Default
`caseIds`	No
`imports`	No
`projectPath`	Yes
`viewportIds`	No

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

C2.9/5.0

Behavior4/5

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

With annotations readOnlyHint=false and destructiveHint=false, the safety profile is partially conveyed Equipment. The description adds useful behavioral context: it requires user authorization, returns a summary and preview, and does not commit to a formal baseline. This exceeds what annotations provide.

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?

Two short sentences with no filler. The primary action and the most important outcome (summary/preview) are front-loaded. It relies on the reader already knowing the tool's context, but the length is appropriate.

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?

The output schema presumably covers the return structure, but the input schema has no descriptions and the description doesn't explain the parameters. No usage scenarios, exclusions, or ordering with sibling tools are provided. For a 4-parameter tool with meaningful semantics, this is incomplete.

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

Parameters1/5

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

Schema description coverage is 0%, and the description mentions no parameter names or roles. projectPath, caseIds, imports, and viewportIds are completely undocumented in both schema and description, so an agent has no guidance on what values to provide.

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 verb ('prepare') and a specific resource ('visual baseline candidate'), and clarifies it returns a summary and preview. The phrase 'does not adopt a formal baseline' distinguishes it from formal approval tools like approve_visual_baseline without naming them.

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 explicit when-to-use or when-not-to-use guidance is given. The statement that it does not adopt a formal baseline implies it is a preparatory step before approval, but the description never says to use it before approve_visual_baseline or before other editing tools. Sibling differentiation is left entirely to the agent.

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

Deploy Server