Skip to main content
Glama
Sign In
teamwork

teamwork

by sondv5
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Teamwork: task comments

list_task_comments
Read-only

Retrieve the full comment thread for a task using its ID. Paginate through responses to review discussions.

Instructions

Read the comment thread of a task.

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": {
      "taskId": "<taskId>"
    },
    "name": "list_task_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
taskIdYesTeamwork task id
pageSizeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.4/5.0
Behavior3/5

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

The description is consistent with the readOnlyHint annotation. It does not add extra behavioral details such as pagination behavior or return format, but the annotation already covers the read-only nature. It adds minimal context beyond that.

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 sentence with no redundant information. It is appropriately concise and front-loaded with the core action.

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 has three parameters including pagination controls and no output schema, the description is minimal. It does not mention that the tool returns a list of comments or how pagination works. However, for a simple read operation, it might be adequate, but it could be more complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is only 33% (only taskId is described). The tool description does not mention the page and pageSize parameters, so it does not compensate for the missing schema descriptions. An agent would not know that page and pageSize are optional pagination controls from the description alone.

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 uses a clear verb 'Read' and a specific resource 'comment thread of a task', making it easy to distinguish from sibling tools like add_task_comment or get_task. It states exactly what the tool does.

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 explicit guidance on when to use this tool versus alternatives. It does not mention that add_task_comment is for writing comments, or that get_task is for task details. The usage context is implied but not stated.

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

Deploy Server

Other Tools