Skip to main content
Glama

get_task_comments

Read-onlyIdempotent

El hilo de comentarios de una tarea, del más viejo al más nuevo.

Los comentarios son la conversación sobre una tarea, y existen sobre todo
para los tableros compartidos: es donde el dueño y el invitado se hablan sin
compartir el workspace. Funcionan igual en una tarea propia.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMáximo (default: 50)
task_idYesID numérico de la tarea
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir = TODOS los workspaces de la persona, en una sola llamada

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered externally. The description adds genuine value with the fixed chronological ordering, which the annotations do not express, but says nothing about pagination limits or result volume.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first line is well front-loaded, but the second paragraph explains what comments conceptually are rather than how the tool behaves, which is padding for a selection decision. It reads as two loosely connected blocks without wasted words per se, but with tangential content.

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 read-only, three-parameter list tool with a fully documented schema and no output schema, the definition covers the resource, its scope and its ordering. The only gap is that it does not sketch the shape of a returned comment or mention that results are capped by limit.

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%, including the default of 50 and the explicit 'Omitir = TODOS los workspaces' note for workspace_id, so the schema already carries parameter meaning. The description adds no parameter-level detail; baseline 3 applies.

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 line states the specific resource ('el hilo de comentarios de una tarea') and the ordering ('del más viejo al más nuevo'), which is a concrete verb+resource statement an agent can act on. It does not explicitly contrast with sibling write tool add_task_comment, so it stops short of full sibling differentiation.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, nor any named alternative. The remark that comments 'existen sobre todo para los tableros compartidos' describes the nature of the resource rather than conditions for calling this tool, so usage must be inferred from the name.

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