Skip to main content
Glama

Post a comment as the AI

kanbini_post_comment

Post a Markdown comment on a kanban card, automatically attributed to AI so it displays an AI badge and remains distinct from human comments.

Instructions

Post a comment on a card. Author is automatically set to 'ai' so it renders with the AI badge in the UI (and is distinguishable from human-written comments). Body is Markdown - put real line breaks between paragraphs and list items. A literal backslash-n renders as the text "\n", not a line break. A card can be given by its id, or by its number (#142, as shown on the card) with boardId (the id or name of the board it is on).

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": {
      "cardId": "<cardId>",
      "body": "<body>"
    },
    "name": "kanbini_post_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
cardIdYes
boardIdNoThe board's id or exact name. Needed when you name a card by number (#142) or a list / label by name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.17.0
    • changedInput schema / properties / boardId / description
      Previous value: -"Only when a card is given by number (#142): the board it is on"New value: +"The board's id or exact name. Needed when you name a card by number (#142) or a list / label by name."
  2. Changed1 schema field changedv0.15.0
    • addedInput schema / properties / boardId
      Added value: +{
      +  "description": "Only when a card is given by number (#142): the board it is on",
      +  "type": "string"
      +}
  3. First observedv0.13.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the forced author attribution and its UI consequence (AI badge, distinguishable from human comments) and warns about a real pitfall — literal backslash-n rendering as text instead of a line break. It omits permissions/access requirements and whether posting notifies anyone, which keeps it out of the top band.

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?

Three tightly packed sentences, front-loaded with the action, then the author-attribution behavior, then the Markdown caveat and card addressing. The backslash-n warning is verbose but earns its place as a common failure mode; nothing is padding.

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?

For a 3-parameter mutation tool with no annotations and no output schema, the description covers attribution behavior, body format, and card addressing well. The main gap is that it never says what comes back from a successful post (e.g., the created comment's id), which matters for follow-up edits via kanbini_update_comment.

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 only 33% (only boardId is documented), but the description compensates substantially: cardId can be a raw id or a #number paired with boardId, and body is Markdown with explicit line-break semantics. Only boardId's 'id or exact name' nuance is left to the schema, so nearly all parameter meaning is conveyed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Post a comment on a card') plus a distinguishing effect: the author is forced to 'ai' and renders with an AI badge, so the agent knows this is an AI-authored creation, not a generic comment write. It does not explicitly name sibling kanbini_update_comment to draw the create-vs-edit line, so it stops short of full differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the verb (use this to add a new comment), and the description does give practical addressing guidance (card by id, or by #number plus boardId). It never states when to prefer kanbini_update_comment instead, nor any preconditions such as needing the card to exist or be accessible.

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