TRAECNclaw MCP

Open TraeCN Workspace

traecn_open_workspace

Opens an absolute local folder path as the active TraeCN workspace and verifies activation before returning, so tasks run against the correct project without repeating the path.

Instructions

Open one absolute local folder path as the active TraeCN workspace and verify it became active before returning. Call before submitting work that depends on a specific project; afterwards do not repeat the path inside the task message.

Input Schema

Name	Required	Description	Default
`path`	Yes	Absolute local folder path.

Output Schema

Name	Required	Description
`cdp`	No	CDP endpoint coordinates for gateway control.
`args`	No	Launch arguments when TraeCN had to be started.
`code`	No	Stable machine-readable result or error code.
`error`	No	Error identifier or diagnostic when the operation failed.
`status`	No	Stable operation or task status.
`taskId`	No	Stable gateway task identifier.
`binPath`	No	TraeCN binary path used by the gateway.
`changed`	No	Whether visible TraeCN state changed.
`command`	No	Launch command when TraeCN had to be started.
`message`	No	Human-readable outcome summary.
`success`	No	Whether the operation succeeded.
`retryable`	No	Whether retrying the same call can succeed later.
`nextAction`	No	Suggested next step after a failure.
`projectPath`	No	Absolute folder path that was opened.
`reusedWindow`	No	Whether an existing window was reused instead of spawning one.
`alreadyRunning`	No	Whether TraeCN was already running.
`conversationId`	No	Stable TraeCN conversation identifier.
`verifiedWorkspace`	No	Workspace identity detected in the TraeCN window, or a compatible gateway path string.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.7.1-glama.1Nov 7, 2026

addedOutput schema / properties / verifiedWorkspace / additionalProperties
```
Added value: +true
```

changedOutput schema / properties / verifiedWorkspace / description

Previous value: -"Workspace path verified inside the TraeCN window."New value: +"Workspace identity detected in the TraeCN window, or a compatible gateway path string."

addedOutput schema / properties / verifiedWorkspace / properties

Added value: +{
+  "folderName": {
+    "description": "Folder name detected in the TraeCN window.",
+    "type": "string"
+  },
+  "rootPath": {
+    "description": "Detected absolute workspace root, or null when unavailable.",
+    "type": [
+      "string",
+      "null"
+    ]
+  }
+}

changedOutput schema / properties / verifiedWorkspace / type

Previous value: -"string"New value: +[
+  "string",
+  "object"
+]

First observedAug 24, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations declare a non-read-only, non-idempotent, non-destructive mutation, and the description adds a real behavioral fact beyond them: the tool verifies activation before returning, implying failure surfaces at call time rather than later. It leaves out what happens to a previously active workspace and whether the selection persists, which matters given idempotentHint=false.

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?

Two tightly written sentences with the action and its verification guarantee first, followed by the usage trigger and the follow-up constraint. Nothing is redundant and nothing is buried.

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

Completeness4/5

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

With an output schema present, return values need no explanation, and the description is sufficient for a one-parameter state-mutating call: what it does, when to call it, and the post-call convention. The only genuine gap is the fate of the prior active workspace and persistence semantics.

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 coverage is 100% and the single property already documents 'Absolute local folder path.' The description only reinforces the constraint that exactly one path is accepted ('one absolute local folder path'), adding minimal meaning beyond the schema.

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 description supplies a specific verb ('Open'), a precisely bounded resource ('one absolute local folder path as the active TraeCN workspace'), and an outcome guarantee ('verify it became active before returning'). No sibling tool touches workspaces, so no disambiguation is owed, and an agent knows exactly what the call accomplishes.

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?

It gives an explicit when-to-use trigger ('before submitting work that depends on a specific project') plus a downstream instruction not to repeat the path in the task message. There are no alternative tools to route to, and no explicit when-not-to-use case, so it falls just short of the top mark.

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