Skip to main content
Glama

get_comments

Read-only

Fetches comments from a Trello card newest first and supports pagination with limit and before to page through older comments.

Instructions

Get the comments on a card, newest first. Page with limit and before (id of the last comment of the previous page).

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

Input Schema

NameRequiredDescriptionDefault
langNoISO 639-1 code of the language the user is writing in (e.g. en, ru, uk). Always pass it: server messages are returned in this language.
limitNo
beforeNo
cardIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real behavioral detail beyond that: deterministic ordering (newest first) and the pagination protocol via limit/before. It does not mention rate limits, empty-result behavior, or deleted/archived comment handling, which keeps it below a 5.

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?

Two short sentences with zero filler; the ordering guarantee is front-loaded and the paging mechanics follow immediately. Nothing is repeated from the schema or annotations.

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 simple read-only list endpoint with no output schema and annotations covering safety, the definition supplies what an agent actually needs to call it: ordering and cursor semantics. What a comment object contains and how to detect the last page are left implicit, which is a small but real gap.

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 25%, so the description must compensate, and it does for the two hardest parameters: it explains that limit drives paging and that before is 'the id of the last comment of the previous page', which the bare schema type string does not convey. cardId and lang are left to the schema, but lang is already documented there and cardId is self-evident.

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 ('Get the comments on a card') plus an ordering guarantee ('newest first'), which is enough to distinguish it from add_comment and from get_card. It stops short of naming a sibling explicitly, but the read/comment pairing is unambiguous.

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 and the pagination instructions — an agent can infer this is the read path for comments versus add_comment. There is no explicit when-to-use/when-not statement and no mention of preconditions such as needing a valid card id.

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