tomatrello-mcp

add_comment

Post a comment to a Trello card by supplying its card ID or short link along with the comment text. Use this action to append feedback or notes directly to any card.

Instructions

Add a comment to a Trello card

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

Input Schema

Name	Required	Description	Default
`cardId`	Yes	Trello card ID or short link
`comment`	Yes	Comment text

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 5, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It states the primary action ('add a comment') but does not disclose side effects, authentication requirements, or whether it returns the created comment. For a simple create operation this is largely sufficient, but it adds no context beyond the action itself.

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?

A single, front-loaded sentence with no extraneous words. Efficiently conveys the action and target without any filler.

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?

Given the tool's simplicity (2 required params, no output schema, no nested objects), the description plus schema cover the essentials. It does not mention return value or authentication, but these are less critical for a basic add operation.

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% for both parameters (cardId and comment), and the description adds no additional parameter meaning. Baseline of 3 applies because the schema already documents the parameters clearly.

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 ('Add'), resource ('comment'), and target ('Trello card'). Clearly distinguishes from sibling tools list_comments, update_comment, and delete_comment via the 'add' verb.

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?

No explicit guidance on when to choose this over sibling tools, but the verb 'add' and the sibling names (list/update/delete) make the usage context implicitly clear. Lacks exclusions, prerequisites, or alternative routing.

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

Deploy Server