Well

Create note

well_create_note

Save a note in the current workspace now, optionally about one company.

Use this tool when the user asks to note, write down or remember a fact about a company or about their work ("Note: Acme wants the mockup by Friday"). A complete order is the yes: the note is saved at once, with no card and no question. Ask only when something it needs is missing: the text, or which company when the user named one you cannot find. A message that starts with "Note:" or "Note :" is always a note, in any language, even when it names a date, a deadline or something to deliver ("Note : Acme veut la maquette pour vendredi"): call this tool, never well_create_task. A task is only for an explicit to-do or reminder the user asks for. An order to add a note whose text is a to-do with a day ("Ajoute une note : rappeler Acme mardi") is that task: save the task alone and do not call this tool for it, also not after the task is saved. One order saves one record.

REQUIRED: body, the note's own text. Leave out the "Note:" prefix and the company's name: "Note: Acme wants the mockup by Friday" saves the body "wants the mockup by Friday" on Acme. OPTIONAL: title, a short title. company_id, the company the note is about, from well_query_records or well_get_entity. A company_id that is not a live company of this workspace fails and nothing is written: ask the user whether to create the company first, never save the note without it. calendar_event_id, one exact stored calendar event id the user selected or named; use an id returned by a calendar read, never infer an event from note text, title or time. A calendar event id that is not a live readable meeting fails and nothing is written. company_id and calendar_event_id cannot be combined.

Change a saved note with well_update_note and delete one with well_delete_note.

Returns { success: true, created, note } on success (created is false when this same call already saved the note), or { success: false, error } on failure.

Input Schema

Name	Required	Description
`body`	Yes	The note's text, without a 'Note:' prefix or the company name.
`title`	No	A short title for the note.
`company_id`	No	The company the note is about.
`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.
`calendar_event_id`	No	The exact stored calendar event the note is about.

Output Schema

Name	Required	Description
`code`	No
`note`	No
`error`	No
`created`	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.

Changed12 schema fields changedOct 28, 2026

addedOutput schema / properties / code
```
Added value: +{
+  "type": "string"
+}
```

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"
+}
```

removedOutput schema / properties / note / properties / body / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / note / properties / body / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / note / properties / company_id / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / note / properties / company_id / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / note / properties / company_name / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / note / properties / company_name / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / note / properties / title / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / note / properties / title / type
```
Added value: +[
+  "string",
+  "null"
+]
```

addedOutput schema / properties / reply_lines

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changed3 schema fields changedOct 22, 2026

addedInput schema / properties / calendar_event_id

Added value: +{
+  "description": "The exact stored calendar event the note is about.",
+  "format": "uuid",
+  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+  "type": "string"
+}

addedOutput schema / properties / note / properties / author

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "full_name": {
+          "type": "string"
+        },
+        "person_id": {
+          "format": "uuid",
+          "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+          "type": "string"
+        }
+      },
+      "required": [
+        "person_id",
+        "full_name"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / properties / note / required

Previous value: -[
-  "note_id",
-  "title",
-  "body",
-  "company_id",
-  "company_name"
-]New value: +[
+  "note_id",
+  "title",
+  "body",
+  "company_id",
+  "company_name",
+  "author"
+]

AddedOct 19, 2026

TDQS

A4.8/5.0

Behavior5/5

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

The annotations already establish that this is a non-readonly, non-destructive, closed-world write, and the description adds meaningful behavior beyond that: the note is saved immediately with no confirmation card, invalid company_id or calendar_event_id writes nothing, company_id and calendar_event_id cannot be combined, and success/failure return shapes are described.

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?

The description is front-loaded with the core action and then provides decision rules and parameter constraints. It is somewhat long and repeats note/task examples in multiple languages, but most sentences earn their place by preventing a specific misclassification.

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?

For an 8-parameter write tool with an output schema and annotations, the description covers the key decision points, failure modes, sibling alternatives, parameter constraints, and return behavior. An agent has enough information to invoke it correctly without needing extra context.

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 coverage is 100%, so the baseline is 3, but the description adds important semantics beyond the schema: strip the 'Note:' prefix and company name from body, source company_id from well_query_records or well_get_entity, use only an exact stored calendar_event_id, and never combine company_id with calendar_event_id. The remaining workspace/conversation/idempotency parameters are covered by the schema rather than the description.

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 states a specific verb and resource: save a note in the current workspace, optionally attached to one company. It distinguishes the tool from nearby siblings by naming well_create_task, well_update_note, and well_delete_note, so an agent can identify its role without opening the schema.

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

Usage Guidelines5/5

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

It gives explicit when-to-use conditions, examples, and an exclusion rule for to-do-like notes that should use well_create_task instead. It also explains when to ask clarifying questions versus saving immediately, which is unusually actionable guidance.

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?