Skip to main content
Glama

Send board comments

well_send_board_comments

Send comments of a board to Well, which applies them on the board in the background as one change that one undo reverts, and records a result on each comment (applied, a question, an answer, or a refusal with its reason).

Use this tool when an editor of the board asks to send its comments. Find the board_comment_id values first with well_list_board_comments.

REQUIRED: canvas_view_id, board_comment_ids (1 to 20 comments of the board: not sent yet, or holding a question that a reply answers).

Only an editor of the board can send. The send is paid from the workspace's balance, like a chat turn. A comment that cannot be sent fails the whole call, and nothing is sent. A comment a reader wrote with no login goes only in a send of its own: a send of several comments leaves it out and sends the rest, and a send of several that are all a reader's sends nothing.

Returns { success: true, batch_id, board_comment_ids } once the send is queued, where board_comment_ids names the comments that went, or { success: false, error } on failure. The results arrive on the comments: read them with well_list_board_comments.

Input Schema

NameRequiredDescriptionDefault
workspace_idNoTarget 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.
canvas_view_idYesThe board, from well_show_canvas or well_render_canvas.
conversation_idNoThe 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_keyNoOptional client-supplied key. A retried write with the same key returns the original result instead of re-applying the operation.
workspace_scopeNoRestrict 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.
board_comment_idsYesThe root comments to send, each once.

Output Schema

NameRequiredDescriptionDefault
codeNo
errorNo
successYes
batch_idNo
reply_linesNo
conversation_idNoThe conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
near_candidatesNo
newly_connectedNoTools 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.
board_comment_idsNo
conversation_id_noteNoPresent only when the server opened a fresh lane, stating that no choice recorded earlier was read.
conversation_id_sourceNoWhere the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.
near_candidates_truncatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • 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"
      +}
    • addedOutput schema / properties / reply_lines
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), it discloses that the send is applied in the background as a single undoable change, that it is charged to the workspace balance, that only an editor may send, and that a single un-sendable comment fails the entire call. It also flags the notable reader-comment exception (sends only in a batch of its own), which is behavior an agent could not infer.

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 core action and effect lead, followed by invocation precondition, authorization/cost, failure semantics, and return shape — a sensible front-loaded order with little filler. The opening sentence is long and clause-heavy, and a few sentences (the reader-comment rules) are dense enough to require a second read.

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 a mutation with side effects, payment implications, and partial-failure semantics, the description covers authorization, cost, atomicity, the reader-comment edge case, and the async result pattern (results land on comments, read them with well_list_board_comments). Even though an output schema exists, the inline description of { success, batch_id, board_comment_ids } vs { success: false, error } adds clarifying value.

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?

With 100% schema coverage the baseline is 3, but the description adds real meaning: the ids must be 1–20 root comments that are either un-sent or holding a question a reply answers, which constrains selection in ways the schema's 'root comments to send, each once' does not. It does not elaborate on conversation_id, idempotency_key, or workspace_scope, leaving those entirely to 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?

States a specific verb and resource ('Send comments of a board to Well') and immediately characterizes the effect: applied in the background as one undoable change, with a recorded result per comment. This clearly separates it from sibling read/write tools such as well_list_board_comments, well_create_board_comment, and well_update_board_comment.

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?

Gives an explicit trigger ('when an editor of the board asks to send its comments') and the prerequisite discovery step ('Find the board_comment_id values first with well_list_board_comments'). It lacks a when-not statement or a pointer to the alternative for non-editors or for plain comment creation, so it falls just short of full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources