Workspace369

Create a note

notes_create

Destructive

Add a new note, to the workspace or to one client's Notes tab (notes_update edits an existing note, notes_search finds one). body takes simple markdown (headings, lists, bold, italic, links). By default it is a workspace note the team sees; is_personal: true makes it private to the caller. client_id (one client, from clients_search) writes it into that client's Notes tab instead (needs permission to edit clients; not with is_personal). folder_id must be a folder in that space, else it is refused; omit it for the default folder. A repeat idempotency_key returns the first note (deduped: true). Returns the new note.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "<title>"
    },
    "name": "notes_create"
  }
}

Input Schema

Name	Required	Description
`body`	No	Note text; simple markdown becomes the editor's formatting.
`tags`	No	Tags for the note.
`title`	Yes	Note title.
`client_id`	No	The client this note is about (from clients_search): writes the note into that client's Notes tab.
`folder_id`	No	Folder in the target space; omit for its default notes folder. A `folderId` from notes_search or notes_get on a note in the same space.
`client_ids`	No	Older form of `client_id`: an array of exactly one client id.
`is_personal`	No	true: a private note only the caller sees; default is a workspace note.
`idempotency_key`	No	Optional. Repeat a call with the same key to avoid doing it twice.

Output Schema

Name	Required	Description	Default
`note`	Yes
`deduped`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 1, 2026

changedInput schema / properties / folder_id / description

Previous value: -"Folder in the target space; omit for its default notes folder."New value: +"Folder in the target space; omit for its default notes folder. A `folderId` from notes_search or notes_get on a note in the same space."

Changed2 schema fields changedNov 1, 2026

addedInput schema / properties / client_id

Added value: +{
+  "description": "The client this note is about (from clients_search): writes the note into that client's Notes tab.",
+  "type": "string"
+}

changedInput schema / properties / client_ids / description

Previous value: -"Exactly one client id: writes the note into that client's Notes tab."New value: +"Older form of `client_id`: an array of exactly one client id."

First observedOct 21, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Goes well beyond the annotations: discloses the client-edit permission requirement, that a `folder_id` outside the target space is refused, that repeats of `idempotency_key` return the first note with `deduped: true`, and the default visibility (team-visible). It does not explain any side effects beyond creation (notifications, activity feed) despite destructiveHint=true, which is a minor gap.

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?

Front-loaded with purpose and sibling disambiguation, then parameter behavior; nearly every clause carries a distinct constraint (permission, refusal, dedupe). It is dense but not padded, though the parenthetical sibling list and the closing 'Returns the new note.' are slightly redundant with the output schema.

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?

With 8 parameters, an output schema, and full annotation coverage, the description supplies everything an agent needs to call it correctly: destination selection, privacy mode, permission requirements, folder validation, and dedupe semantics. Return values are delegated appropriately to the output schema.

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 already 100%, yet the description still adds meaning the schema lacks: the cross-space validation rule for `folder_id` and its fallback to the default folder, the permission gate and `is_personal` incompatibility for `client_id`, and markdown support in `body`. `tags` and the legacy `client_ids` are left to the schema only.

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?

States a specific verb and resource ('Add a new note') plus the two possible destinations (workspace or a client's Notes tab), and explicitly names the siblings it is not (notes_update edits, notes_search finds). An agent can distinguish it from the other notes tools without opening a 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?

Gives explicit routing rules: default is a workspace note the team sees, `is_personal: true` makes it private, `client_id` writes into that client's Notes tab, and the two modes are mutually exclusive ('not with `is_personal`'). It also names prerequisites (permission to edit clients) and the alternative tools by name.

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

All Workspace369 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.