TRAECNclaw MCP

Create TraeCN Conversation

traecn_create_conversation

Prepares a fresh TraeCN conversation for a new context by reusing an empty draft or creating another context and returning a native conversation identity when allocated.

Instructions

Prepare a fresh TraeCN conversation for a genuinely new context. Returns a native conversation identity when TraeCN has allocated it; an empty draft returns conversationId=null and creationDeferred=true until its first message. Reuses an already-empty draft; otherwise creates another context. Call once per new context.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`code`	No	Stable machine-readable result or error code.
`error`	No	Error identifier or diagnostic when the operation failed.
`fresh`	No	Whether the active context is ready for a first message.
`action`	No	Conversation operation performed.
`status`	No	Stable operation or task status.
`taskId`	No	Stable gateway task identifier.
`changed`	No	Whether visible TraeCN state changed.
`deleted`	No	Number of conversations removed (delete only).
`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.
`actualTitle`	No	Title actually visible at decision time (delete mismatch only).
`recoverable`	No	Always false for deletion; the gateway cannot restore conversations.
`expectedTitle`	No	Title compared against the visible conversation (delete mismatch only).
`conversationId`	No	Native identity when allocated; null for an empty draft.
`creationDeferred`	No	True when TraeCN will allocate the conversation identity on its first message.

Schema Changelog

Changes observed during successful MCP inspections.

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

changedOutput schema / description

Previous value: -"Created conversation operation outcome."New value: +"Fresh conversation or empty draft awaiting a native identity."

changedOutput schema / properties / conversationId / description

Previous value: -"Stable TraeCN conversation identifier."New value: +"Native identity when allocated; null for an empty draft."

changedOutput schema / properties / conversationId / type

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

addedOutput schema / properties / creationDeferred

Added value: +{
+  "description": "True when TraeCN will allocate the conversation identity on its first message.",
+  "type": "boolean"
+}

addedOutput schema / properties / fresh

Added value: +{
+  "description": "Whether the active context is ready for a first message.",
+  "type": "boolean"
+}

First observedAug 24, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare this as a non-read-only, non-idempotent, non-destructive call. The description goes meaningfully beyond that by disclosing deferred allocation (conversationId=null, creationDeferred=true until first message) and the reuse-versus-create behavior for empty drafts, which an agent could not infer from annotations alone.

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?

Three compact sentences, front-loaded with the purpose, followed by return behavior and the calling rule. Slightly dense phrasing ('until its first message') but no wasted sentences.

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?

For a zero-parameter creation tool with an output schema, the description covers the one thing the schema cannot: the deferred-allocation lifecycle and draft-reuse rule. Complete enough to call correctly; only explicit sibling routing is missing.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description's mention of conversationId/creationDeferred refers to outputs, not inputs.

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?

States a specific verb and resource ('Prepare a fresh TraeCN conversation') plus the scoping condition ('genuinely new context'). It is clearly distinct from siblings like traecn_select_conversation or traecn_list_conversations, though it never names those alternatives explicitly.

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

Usage Guidelines3/5

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

'Call once per new context' gives a usage cue, and 'genuinely new context' implies not to call it when reusing an existing one. However, it never names the sibling to use instead (e.g. traecn_select_conversation) nor states explicit exclusions, leaving routing to inference.

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