Skip to main content
Glama
Sign In

Workspace369

by com.workspace369
OverviewDiscussionsAdmin

Read a task's comments

tasks_comments_list
Read-onlyIdempotent

List the comments on a task, newest first, with author and time. Takes board_id and task_id from tasks_search. Attachments are reported as a count, not urls. Read-only. Returns comments; add one with tasks_comment_add.

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": {
      "board_id": "<board_id>",
      "task_id": "<task_id>"
    },
    "name": "tasks_comments_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoComments to return (default 50, max 100).
task_idYesTask id (from tasks_search).
board_idYesBoard the task is on: the `board_id` on the task's tasks_search row.

Output Schema

NameRequiredDescriptionDefault
commentsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / board_id / description
      Previous value: -"Board the task is on. Use the `id` that task_boards_list returns."New value: +"Board the task is on: the `board_id` on the task's tasks_search row."
  2. Changed1 schema field changed
    • changedInput schema / properties / board_id / description
      Previous value: -"Board the task is on."New value: +"Board the task is on. Use the `id` that task_boards_list returns."
  3. Changed2 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of results to return."New value: +"Comments to return (default 50, max 100)."
    • changedInput schema / properties / task_id / description
      Previous value: -"Task id."New value: +"Task id (from tasks_search)."
  4. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive, yet the description adds real behavior: newest-first ordering, attachments surfaced as a count rather than urls, and the top-level `comments` key. That is context annotations cannot express.

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?

Four short sentences, none wasted: purpose and ordering first, parameter provenance second, data-shape caveat third, then the sibling redirect. Every clause carries information.

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?

An output schema exists so return values needn't be enumerated, and the description still flags the attachment-count nuance and result key. For a simple read tool this is essentially complete, with only minor gaps around pagination/limit behavior.

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% and the schema already documents all three parameters, including that board_id/task_id come from tasks_search. The description mostly restates that provenance and says nothing about `limit` handling, so it adds little over the schema — baseline 3.

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?

States a specific verb and resource ('List the comments on a task') plus ordering ('newest first') and returned fields ('author and time'). It is clearly distinguishable from tasks_comment_add and tasks_search mentioned in the same breath.

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

Usage Guidelines4/5

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

Tells the agent where to obtain the required ids ('from tasks_search') and names the sibling for the opposite action ('add one with tasks_comment_add'). No explicit exclusion or precondition beyond that, but the routing context is clear.

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

All Workspace369 toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources