Skip to main content
Glama

comment_list

Read-onlyIdempotent

Fetch all comments on a task in chronological order. Provide the task ID to get the full comment history.

Instructions

List all comments on a task in chronological order.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYesTask ID

Implementation Reference

  • Schema/definition for the comment_list tool: name, description, annotations, and inputSchema requiring task_id (integer).
    {
      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'],
      },
    },
  • Handler function handleCommentList that queries comments by task_id ordered by created_at ASC.
    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);
    }
  • Exported handlers record mapping 'comment_list' to handleCommentList.
    export const handlers: Record<string, ToolHandler> = {
      comment_add: handleCommentAdd,
      comment_list: handleCommentList,
    };
  • src/index.ts:23-35 (registration)
    Registration of comment tool definitions (including comment_list) into ALL_TOOLS array.
    const ALL_TOOLS: Tool[] = [
      ...projectDefs,
      ...epicDefs,
      ...taskDefs,
      ...subtaskDefs,
      ...noteDefs,
      ...commentDefs,
      ...templateDefs,
      ...dashboardDefs,
      ...searchDefs,
      ...activityDefs,
      ...exportImportDefs,
    ];
  • src/index.ts:37-49 (registration)
    Registration of comment handlers (including comment_list) into ALL_HANDLERS record.
    const ALL_HANDLERS: Record<string, (args: Record<string, unknown>) => unknown> = {
      ...projectHandlers,
      ...epicHandlers,
      ...taskHandlers,
      ...subtaskHandlers,
      ...noteHandlers,
      ...commentHandlers,
      ...templateHandlers,
      ...dashboardHandlers,
      ...searchHandlers,
      ...activityHandlers,
      ...exportImportHandlers,
    };
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds that results are in chronological order, but does not disclose potential pagination, performance, or error behavior. The description adds marginal value beyond annotations.

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 consists of a single, well-structured sentence that immediately conveys the tool's purpose and ordering. No redundant or superfluous words.

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 simplicity of the tool (one required parameter, no output schema, already well-annotated), the description provides a basic, albeit minimal, understanding. It does not explain return format, pagination, or behavior when task_id is invalid, which could be considered gaps, but the tool's simplicity mitigates this.

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 coverage is 100% with the parameter 'task_id' described as 'Task ID'. The description does not elaborate on this field or add any additional meaning beyond the schema definition. Baseline score of 3 is appropriate.

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?

The description clearly states the action ('List') and resource ('comments on a task') with specified ordering ('chronological order'). It unambiguously distinguishes from sibling tools like comment_add (create) and note_list (different resource).

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?

The description implies usage for viewing comments but does not explicitly state when to avoid or compare with alternative tools (e.g., comment_add for creation, or note_search for searching notes). No exclusionary guidance is provided.

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