Skip to main content
Glama

Add a comment to a post

note_comment

Adds a comment to an existing noticeboard post as the signed-in member, notifying the author and takers; use it to reply on a post rather than start a new topic.

Instructions

Adds a comment to an existing noticeboard post as the signed-in member and pushes a notification to the post author and the takers (not to you). Use it to reply on a post; to start a new topic use note_create, and for the live conversation use chat_send. The answer holds the created comment (with its id, authorName and authorColor) and a warning when the push delivery could not be confirmed. Returns 404 announcement_not_found for an unknown post.

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": {
      "id": "<id>",
      "content": "<content>"
    },
    "name": "note_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesId of the post to comment on, from notes_list.
wgCodeNoShare code of the flat (code from wg_list). Leave it out when the account belongs to one flat.
contentYesText of the comment.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • addedInput schema / properties / content / description
      Added value: +"Text of the comment."
    • addedInput schema / properties / id / description
      Added value: +"Id of the post to comment on, from notes_list."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (which only state it is a non-idempotent, non-destructive write), the description discloses the real side effect: a push notification to the post author and takers but not to the caller. It also discloses a failure mode (a warning when push delivery is unconfirmed) and the 404 announcement_not_found error for an unknown post.

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 sentences, each doing distinct work: purpose, sibling routing, return/error behavior. The purpose and side-effect information is front-loaded and no sentence is filler.

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 no output schema, the description carries the return-value burden and does so: created comment with id, authorName, authorColor, plus a delivery warning and the 404 case. Combined with three fully described parameters and annotations, an agent has everything needed to call it correctly.

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 description coverage is 100% and the schema already explains id (from notes_list), wgCode (from wg_list, omit for single-flat accounts) and content. The description adds little parameter meaning beyond tying an unknown id to the 404 error, so it sits at the baseline for a fully documented 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?

The description uses a specific verb and resource ("Adds a comment to an existing noticeboard post") and specifies the acting identity ("as the signed-in member"). It also names the two nearest siblings, note_create and chat_send, so an agent can distinguish this tool without opening another 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 routing: reply on an existing post with this tool, start a new topic with note_create, hold live conversation with chat_send. Nothing about when to choose among these is left to inference.

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