Well

Create chat conversation

well_create_chat_conversation

Create one empty conversation owned by the current member. An optional title names it. This saves the conversation without sending a message or running an assistant turn.

Input Schema

Name	Required	Description
`title`	No
`workspace_id`	No	Target workspace. Omit when the token authorizes one workspace. Required when it authorizes several — a write lands in exactly one workspace and this call would not say which.
`conversation_id`	No	The conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation.
`idempotency_key`	No	Optional client-supplied key. A retried write with the same key returns the original result instead of re-applying the operation.
`workspace_scope`	No	Restrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace.

Output Schema

Name	Required	Description
`code`	No
`data`	No
`error`	No
`success`	Yes
`reply_lines`	No
`conversation_id`	No	The conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
`near_candidates`	No
`newly_connected`	No	Tools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later.
`conversation_id_note`	No	Present only when the server opened a fresh lane, stating that no choice recorded earlier was read.
`conversation_id_source`	No	Where the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.
`near_candidates_truncated`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 1, 2026

addedOutput schema / properties / data / properties / attributes / properties / notes
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

changed

Output schema / properties / data / properties / attributes / properties / tabs / items / properties / destinationId / enum

Previous value: -[
-  "new_tab",
-  "workflows",
-  "tasks",
-  "graph",
-  "boards",
-  "projects",
-  "people",
-  "companies",
-  "invoices",
-  "transactions",
-  "accounts",
-  "account_balances",
-  "payment_means",
-  "supplier_payment_terms",
-  "ledger_accounts",
-  "journals",
-  "journal_entries",
-  "tax_rates",
-  "categories",
-  "documents",
-  "notes",
-  "payslips",
-  "calendar_events",
-  "emails",
-  "media",
-  "connectors",
-  "locations",
-  "web_links",
-  "phones",
-  "members",
-  "billing",
-  "settings",
-  "blueprint_runs",
-  "chat_conversations",
-  "billing_events",
-  "activities",
-  "invoice_items",
-  "invoice_payment_means",
-  "invoice_transactions",
-  "cards",
-  "checks",
-  "exchange_rates",
-  "memberships",
-  "record_workspaces",
-  "connector_install",
-  "mcp_install",
-  "record"
-]New value: +[
+  "new_tab",
+  "workflows",
+  "tasks",
+  "graph",
+  "boards",
+  "projects",
+  "people",
+  "companies",
+  "invoices",
+  "transactions",
+  "accounts",
+  "account_balances",
+  "payment_means",
+  "supplier_payment_terms",
+  "ledger_accounts",
+  "journals",
+  "journal_entries",
+  "tax_rates",
+  "categories",
+  "documents",
+  "notes",
+  "payslips",
+  "calendar_events",
+  "emails",
+  "media",
+  "connectors",
+  "locations",
+  "web_links",
+  "phones",
+  "members",
+  "billing",
+  "settings",
+  "blueprint_runs",
+  "chat_conversations",
+  "billing_events",
+  "activities",
+  "invoice_items",
+  "invoice_payment_means",
+  "invoice_transactions",
+  "cards",
+  "checks",
+  "exchange_rates",
+  "memberships",
+  "record_workspaces",
+  "connector_install",
+  "mcp_install",
+  "meeting_capture",
+  "record"
+]

changedOutput schema / properties / data / properties / attributes / required

Previous value: -[
-  "title",
-  "mode",
-  "page_path",
-  "tabs",
-  "active_tab_key",
-  "total_tokens",
-  "created_at",
-  "updated_at"
-]New value: +[
+  "title",
+  "notes",
+  "mode",
+  "page_path",
+  "tabs",
+  "active_tab_key",
+  "total_tokens",
+  "created_at",
+  "updated_at"
+]

Changed14 schema fields changedOct 28, 2026
- addedOutput schema / properties / code
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / properties / data / properties / attributes / properties / active_tab_key / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / properties / attributes / properties / active_tab_key / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / properties / attributes / properties / mode / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / properties / attributes / properties / mode / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / properties / attributes / properties / page_path / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / properties / attributes / properties / page_path / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / properties / attributes / properties / title / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / properties / attributes / properties / title / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / properties / attributes / properties / updated_at / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / properties / attributes / properties / updated_at / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- addedOutput schema / properties / near_candidates
```
Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "company_id": {
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "company_id",
+      "name"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
```
- addedOutput schema / properties / near_candidates_truncated
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / reply_lines
```
Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
```

Changed1 schema field changedOct 22, 2026

changed

Output schema / properties / data / properties / attributes / properties / tabs / items / properties / destinationId / enum

Previous value: -[
-  "new_tab",
-  "workflows",
-  "tasks",
-  "graph",
-  "boards",
-  "projects",
-  "people",
-  "companies",
-  "invoices",
-  "transactions",
-  "accounts",
-  "account_balances",
-  "payment_means",
-  "ledger_accounts",
-  "journals",
-  "journal_entries",
-  "tax_rates",
-  "categories",
-  "documents",
-  "notes",
-  "payslips",
-  "calendar_events",
-  "emails",
-  "media",
-  "connectors",
-  "locations",
-  "web_links",
-  "phones",
-  "members",
-  "billing",
-  "settings",
-  "blueprint_runs",
-  "chat_conversations",
-  "billing_events",
-  "activities",
-  "invoice_items",
-  "invoice_payment_means",
-  "invoice_transactions",
-  "cards",
-  "checks",
-  "exchange_rates",
-  "memberships",
-  "record_workspaces",
-  "connector_install",
-  "mcp_install",
-  "record"
-]New value: +[
+  "new_tab",
+  "workflows",
+  "tasks",
+  "graph",
+  "boards",
+  "projects",
+  "people",
+  "companies",
+  "invoices",
+  "transactions",
+  "accounts",
+  "account_balances",
+  "payment_means",
+  "supplier_payment_terms",
+  "ledger_accounts",
+  "journals",
+  "journal_entries",
+  "tax_rates",
+  "categories",
+  "documents",
+  "notes",
+  "payslips",
+  "calendar_events",
+  "emails",
+  "media",
+  "connectors",
+  "locations",
+  "web_links",
+  "phones",
+  "members",
+  "billing",
+  "settings",
+  "blueprint_runs",
+  "chat_conversations",
+  "billing_events",
+  "activities",
+  "invoice_items",
+  "invoice_payment_means",
+  "invoice_transactions",
+  "cards",
+  "checks",
+  "exchange_rates",
+  "memberships",
+  "record_workspaces",
+  "connector_install",
+  "mcp_install",
+  "record"
+]

AddedOct 21, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the description's job is to add nuance. It does: the result is empty, ownership is bound to the current member, and no assistant turn is triggered — a meaningful side-effect disclosure beyond the annotations. It stops short of saying what happens on duplicate creates, though the idempotency_key parameter in the schema covers retries.

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?

Three short sentences, no repetition, and the defining constraint (empty, saved, no message) is front-loaded. Every sentence earns its place.

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 not be explained, and the annotations cover the safety profile, so the remaining burden is scope and side effects — both addressed. The omission is the multi-workspace write constraint, which lives only in the schema text.

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 80% and the parameter descriptions are long and specific (workspace_id, conversation_id, idempotency_key, workspace_scope all carry real explanation). The description only confirms that title is optional, so it barely improves on the schema — the 3 baseline applies.

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 ('Create one empty conversation') plus an ownership scope ('owned by the current member'), which is more precise than the title alone. It does not explicitly contrast with the obvious siblings (well_update_chat_conversation, well_delete_chat_conversation, well_send_message), so an agent must infer the boundary.

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?

'This saves the conversation without sending a message or running an assistant turn' implicitly routes message-sending work elsewhere and warns that this is a bare create. Clear context for when this tool applies, but no sibling is named and no exclusions are stated explicitly.

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

All Well tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?