Skip to main content
Glama

add_task_comment

Escribe un comentario en una tarea. Queda firmado con el usuario del token, y lo ve todo el que pueda abrir la tarea — incluido quien tenga prestado un tablero donde la tarea entre.

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": {
      "task_id": "<task_id>",
      "cuerpo": "<cuerpo>"
    },
    "name": "add_task_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
cuerpoYesEl texto del comentario
task_idYesID numérico de la tarea
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir si el token ya tiene workspace fijo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare the write profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true), so the bar is lower, and the description still adds real context: the comment is attributed to the token's user and is visible to everyone who can open the task, including users of a borrowed board. That audience/attribution disclosure is exactly the kind of side effect an agent needs before writing. It does not mention error conditions or whether re-posting duplicates, despite idempotentHint=false.

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 sentences, zero waste, with the action front-loaded and the behavioral consequence immediately after. Every clause carries information the schema and annotations do not.

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 three-parameter mutation with no output schema, full schema coverage, and existing annotations, the description covers the essential action and its visibility side effect. Minor gaps are the return value or confirmation behavior and no note on what happens if the same comment is submitted twice.

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%, so task_id, cuerpo, and workspace_id are already documented in the schema, establishing a baseline of 3. The description adds no syntax, format, or fallback detail for workspace_id beyond what the schema states.

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?

The opening sentence gives a specific verb plus resource ("Escribe un comentario en una tarea"), which makes the write action unambiguous against the read-side sibling get_task_comments. It stops short of naming any sibling or contrasting behavior, so it does not fully earn a 5 on 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 when a comment must be posted on a task — but there is no explicit when-to-use/when-not guidance and no alternative is named. The visibility note is useful context rather than selection guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources