Skip to main content
Glama

Read the noticeboard

notes_list
Read-onlyIdempotent

Lists noticeboard posts with pinning, status, reactions, takers, and comments, returning post IDs and updatedAt timestamps so you can find the right post to update or read.

Instructions

Lists the flat noticeboard: member-written posts, pinned first, then newest first (max 300). Each post carries kind, status, updatedAt, reactionCounts, myReactions, takers (members who reacted with take) and its comments. Finished posts (resolved, or info/decision) drop off the board 30 days after their last activity unless pinned; open questions, problems and requests stay. A post with source chore_swap is a swap request for a chore; chore_update with a new assignee or chore_complete closes it. Use this to find post ids and updatedAt for note_update; use note_comments to read the comments of one post by id.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "notes_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
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. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and no destructive behavior, so the safety profile is covered; the description usefully adds the 300-post cap, ordering, retention window and the exact fields each post carries. It stops short of pagination or truncation behavior when the cap is hit, so it is solid context rather than exceptional.

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 the core action and ordering, then detail in decreasing priority; no filler sentences. The chore_swap / chore_update closing sentence is dense and slightly tangential to a list operation, keeping it just short of a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 carries the burden of describing return values—which it does by enumerating kind, status, updatedAt, reactionCounts, myReactions, takers and comments. The only gap is lack of any pagination or truncation guidance when the 300 cap is exceeded.

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?

The single wgCode parameter already has full schema coverage including a pattern and the "leave it out when the account belongs to one flat" rule, and the description adds nothing about it. With schema coverage at 100%, the baseline of 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?

States a specific verb and resource ("Lists the flat noticeboard: member-written posts") and immediately qualifies scope with ordering and cap ("pinned first, then newest first (max 300)"). This is clearly distinguishable from note_comments and note_update, which the description also names.

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?

Explicitly routes the agent: "Use this to find post ids and updatedAt for note_update; use note_comments to read the comments of one post by id." It also supplies when-not conditions in the form of retention rules—finished posts drop off after 30 days unless pinned, while open questions, problems and requests stay.

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