Skip to main content
Glama

comment_list

Read-onlyIdempotent

Retrieve all comments for a specific task in chronological order to track discussion history and decision-making within project management workflows.

Instructions

List all comments on a task in chronological order.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYesTask ID

Implementation Reference

  • The handler function that retrieves comments for a specific task from the database.
    function handleCommentList(args: Record<string, unknown>) {
      const db = getDb();
      const taskId = args.task_id as number;
    
      return db
        .prepare('SELECT * FROM comments WHERE task_id = ? ORDER BY created_at ASC')
        .all(taskId);
    }
  • The definition and schema for the 'comment_list' tool.
    {
      name: 'comment_list',
      description: 'List all comments on a task in chronological order.',
      annotations: { title: 'List Comments', readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: false },
      inputSchema: {
        type: 'object',
        properties: {
          task_id: { type: 'integer', description: 'Task ID' },
        },
        required: ['task_id'],
      },
    },
  • Registration of the 'comment_list' handler in the handlers mapping.
    export const handlers: Record<string, ToolHandler> = {
      comment_add: handleCommentAdd,
      comment_list: handleCommentList,
    };
Behavior3/5

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

Annotations provide readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false, covering safety and idempotency. The description adds the chronological ordering behavior, which is useful context not in annotations. However, it doesn't disclose other traits like pagination, rate limits, or authentication needs.

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?

The description is a single, efficient sentence that front-loads the core purpose ('List all comments on a task') and adds a useful detail ('in chronological order') without any wasted words or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (one parameter, no output schema) and rich annotations, the description is minimally adequate. It covers the basic purpose and ordering but lacks details on output format, error handling, or integration with siblings, leaving some gaps for an AI agent.

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%, with the single parameter 'task_id' documented as 'Task ID'. The description implies this parameter is used to specify the task but adds no further meaning beyond what the schema provides, such as format examples or constraints.

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 description clearly states the action ('List all comments') and resource ('on a task'), with the additional detail of chronological ordering. It distinguishes from general comment tools but doesn't explicitly differentiate from sibling tools like 'note_list' or 'activity_log' which might also list comments or related content.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'comment_add' for adding comments or 'note_list' for listing notes, nor does it specify prerequisites or contexts for use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/spranab/saga-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server