Skip to main content
Glama

Read the comments on a post

note_comments
Read-onlyIdempotent

Reads the comments of a single noticeboard post in chronological order, returning each comment's author, content, and timestamp. Use it when you need comments for one post instead of all posts.

Instructions

Reads the comments of one noticeboard post, oldest first (max 500), each with id, memberId, content, createdAt, authorName and authorColor. Use it when you only need one post; notes_list already embeds comments for all posts. To add a comment instead of reading them, use note_comment. Returns 404 announcement_not_found for an unknown post id.

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>"
    },
    "name": "note_comments"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • addedInput schema / properties / id / description
      Added value: +"Id of the post, 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?

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantive behavior on top: result ordering, a 500-item ceiling, the exact fields returned, and the specific error code for an unknown post id.

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, front-loaded with the core action and scope, then routing guidance, then the failure mode. No redundant or filler wording.

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?

No output schema exists, so the description compensates by enumerating returned fields and the 404 announcement_not_found case; combined with a fully documented two-parameter schema, 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 both parameters are already documented in the schema (id sourced from notes_list, wgCode omittable for single-flat accounts), so the description adds no meaning beyond it. Baseline 3 applies.

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?

Names a specific verb and resource ('Reads the comments of one noticeboard post') plus ordering ('oldest first') and a cap ('max 500'), which lets an agent distinguish it from notes_list and note_comment 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 when-to-use ('when you only need one post'), an explicit alternative with its behavior ('notes_list already embeds comments for all posts'), and an explicit when-not with redirection ('To add a comment instead of reading them, use note_comment').

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