Skip to main content
Glama

Write a post

note_create

Posts an announcement, question, or request to the shared flat noticeboard and sends a push notification to other members.

Instructions

Posts a new message to the flat noticeboard as the signed-in member and sends a push notification to the other members. Use it for announcements, questions or requests to the whole flat; to ask for a chore to be taken over use chore_swap_request, to reply on an existing post use note_comment, and for the live conversation use chat_send. The answer holds the created announcement and a warning when the push delivery could not be confirmed. An imageUrl that is not an app-issued upload of this flat fails with image_invalid; an upload that was deleted fails with image_removed.

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

Input Schema

NameRequiredDescriptionDefault
kindNoType of the post. info and decision are finished posts that fade from the board; question, problem and request stay on the board until resolved. Defaults to info.info
wgCodeNoShare code of the flat (code from wg_list). Leave it out when the account belongs to one flat.
contentYesText of the post, shown as written on the noticeboard.
imageUrlNoOptional image attached to the post. Must be the URL of an image already uploaded to this flat through the ManaWG app; arbitrary URLs are rejected. Omit for a text-only post.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.1
    • addedInput schema / properties / content / description
      Added value: +"Text of the post, shown as written on the noticeboard."
    • addedInput schema / properties / imageUrl / description
      Added value: +"Optional image attached to the post. Must be the URL of an image already uploaded to this flat through the ManaWG app; arbitrary URLs are rejected. Omit for a text-only post."
    • addedInput schema / properties / kind / description
      Added value: +"Type of the post. info and decision are finished posts that fade from the board; question, problem and request stay on the board until resolved. Defaults to info."
  2. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

The annotations state only that this is a non-idempotent write that is not destructive; the description adds the real behavioral context: a push notification goes out to the other members, the response holds the created post plus a warning when push delivery could not be confirmed, and two named failure modes are given for imageUrl (image_invalid for a URL that is not an app-issued upload of this flat, image_removed for a deleted upload). These are concrete facts the agent cannot infer from the annotations.

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?

Four sentences with no wasted wording, ordered usefully: what it does, when to use it, what comes back, and what fails. The routing sentence includes only the alternatives that matter for a noticeboard write.

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 explains the return value itself: the created announcement plus a push-delivery warning. It also covers the required wgCode case implicitly through the schema default, reports both error codes specific to imageUrl, and describes the side effect. Nothing needed to call it 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 here is 3, because the schema already documents kind, wgCode, content and imageUrl, including the enum and its default. The description still adds meaning beyond that: it says parameter values cause errors at invocation time, distinguishing image_invalid from image_removed, which the schema does not.

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 names the exact verb and resource ('Posts a new message to the flat noticeboard') and states the two effects of calling it: posting as the signed-in member and pushing a notification to the other members. That is enough to tell it apart from note_comment, chat_send and chore_swap_request without reading 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?

The description says what this tool is for (announcements, questions and requests to the whole flat) and routes the agent to the alternative that fits each other case: chore_swap_request for taking over a chore, note_comment for replying on an existing post, and chat_send for live conversation. The exclusions are explicit rather than implied.

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