Skip to main content
Glama

Set a reaction

note_react
Idempotent

Set or remove seen, ok, or take reactions on a noticeboard post. Taking a post signals you will handle it and gets you notified about new comments and resolution.

Instructions

Sets or removes your own seen, ok or take reaction on one noticeboard post. seen means you read it, ok means you agree, take means you will handle it: it lets you resolve the post via note_update and makes you a taker, who is notified about new comments and when the post is resolved. Reaction kinds are independent, so you can hold several on one post. Use it to react, not to write text; use note_comment to reply. The call states the desired end state, so repeating it is safe and changes nothing. Reactions notify nobody. Any flat member may call it. Returns the reaction and active as stored. Setting take on an already resolved post fails with 409 announcement_resolved; reopen it first with note_update. 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>",
      "reaction": "<reaction>",
      "active": "<active>"
    },
    "name": "note_react"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesId of the post to react to, from notes_list.
activeYestrue sets your reaction, false removes it. Removing one you never set is a no-op.
wgCodeNoShare code of the flat (code from wg_list). Leave it out when the account belongs to one flat.
reactionYesWhich reaction kind to set or remove. Kinds are independent: setting one does not clear another.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.1
    • addedInput schema / properties / active / description
      Added value: +"true sets your reaction, false removes it. Removing one you never set is a no-op."
    • addedInput schema / properties / id / description
      Added value: +"Id of the post to react to, from notes_list."
    • addedInput schema / properties / reaction / description
      Added value: +"Which reaction kind to set or remove. Kinds are independent: setting one does not clear another."
  2. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations it discloses idempotency semantics (desired-end-state call, safe to repeat), notification behavior ('Reactions notify nobody'), the permission model ('Any flat member may call it'), the return payload, and two concrete failure modes (409 announcement_resolved, 404 announcement_not_found). This is substantially more than readOnlyHint/idempotentHint/destructiveHint convey.

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 the sibling routing, and nearly every sentence carries operational information. It is dense and slightly repetitive around return values ('Returns the reaction and active as stored' plus a second 'Returns 404...' sentence), which keeps it from a 5.

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 supplies the response shape, the notification and permission context, and the two error paths an agent could hit. Nothing needed to call this four-parameter mutation correctly is missing.

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 100%, so the baseline is 3; the description adds real meaning by defining what each enum value implies ('seen means you read it, ok means you agree, take means you will handle it' and the taker/notification consequence). It does not discuss wgCode, so it stops short of full coverage.

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 first sentence names a specific verb pair (sets or removes) and a specific resource (seen/ok/take reaction on one noticeboard post), and the later clause 'use note_comment to reply' separates it from the text-writing sibling. An agent can identify the operation without opening the 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 an explicit use/do-not-use split ('Use it to react, not to write text; use note_comment to reply'), plus a concrete workflow rule: setting take lets you resolve via note_update and requires reopening a resolved post first. Alternative tools and preconditions are both named.

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