Skip to main content
Glama

Coline

List task relations

list_task_relations
Read-onlyIdempotent

Lists a task's parent, sub-tasks, blockers, the tasks it blocks, related tasks and duplicates.

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": {
      "workspace": "<workspace>",
      "taskboardId": "<taskboardId>",
      "taskId": "<taskId>"
    },
    "name": "list_task_relations"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYesTask id from list_tasks, find_task or get_task.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
taskboardIdYesBoard id from list_boards.

Output Schema

NameRequiredDescriptionDefault
parentYes
relatedYes
blockersYes
blockingYes
subtasksYes
duplicateOfYes
duplicatedByYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description's added value is the enumeration of the relation categories that come back, which tells the agent what the payload contains. It says nothing about behavior when no relations exist, ordering, or volume, so it adds only modest context beyond the annotations and the output schema.

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

Conciseness4/5

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

A single front-loaded sentence with no filler; every clause names a distinct relation type. It could be slightly easier to scan as a list, but that is a minor stylistic point rather than wasted text.

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?

The tool is simple: three required ids, an output schema, and full annotation coverage, so much of the burden is already discharged elsewhere. The description covers what is returned but leaves out empty-result behavior and confirmations that the enumeration is exhaustive, which leaves it adequate rather than complete.

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% and all three parameters (taskId, workspace, taskboardId) carry their own descriptions naming the tools that supply them. The description adds no parameter-level meaning, so the 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 description states a specific verb and resource ("Lists a task's ...") and then enumerates exactly which relation kinds are returned: parent, sub-tasks, blockers, blocked tasks, related tasks, duplicates. That is a clear, non-tautological purpose. It stops short of distinguishing itself from sibling mutation tools like remove_task_relation or set_task_parent, which keeps it at a 4.

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. The description never says to call this to inspect or verify relations before using add_task_blocker, set_task_parent, or remove_task_relation, nor does it mention any prerequisite such as having a task id from find_task. The read-only nature is only inferable from the annotations.

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