Skip to main content
Glama

Coline

Link two tasks

add_task_blocker

Records that one task blocks another (kind blocks: fromTaskId blocks toTaskId), is related to it, or duplicates it. Both tasks must be in the workspace.

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>",
      "fromTaskId": "<fromTaskId>",
      "toTaskId": "<toTaskId>"
    },
    "name": "add_task_blocker"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoblocks
toTaskIdYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
fromTaskIdYes
taskboardIdYesBoard that has fromTaskId. toTaskId may be on another board.

Output Schema

NameRequiredDescriptionDefault
kindYes
taskYes
relationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare a non-read-only, non-idempotent, non-destructive mutation, so the safety profile is carried structurally. The description adds a real constraint ("Both tasks must be in the workspace") and clarifies that relations are directional (fromTaskId is the blocker), but says nothing about what happens when the relation already exists or how failures surface.

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?

Two sentences, effect first then constraint, with no filler. The middle clause ("is related to it, or duplicates it") reads slightly awkwardly because the subject becomes ambiguous, a small clarity cost in otherwise tight prose.

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?

The tool is a five-parameter mutation with four required fields and an output schema, so return values need not be described. The description covers the essential semantics (kind, direction, workspace constraint); only duplicate-handling and one-way vs. symmetric behavior are left unstated.

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

Parameters4/5

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

With only 40% schema description coverage, the description usefully compensates: it maps the `kind` enum to its semantics and spells out the direction convention (fromTaskId blocks toTaskId). It leaves `workspace` and `taskboardId` to the schema, which is acceptable since those carry inline descriptions.

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?

States a specific verb ("records") and a concrete resource (a relationship between two tasks), and enumerates the three relationship kinds, so an agent knows exactly what gets created. It does not explicitly distinguish itself from the related read-side sibling (list_task_relations), which keeps it short of a 5.

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?

Usage is only implied by the description of the effect; there is no explicit "use this when..." or "do not use this for..." guidance, nor mention of an alternative for reading or removing existing relations. The stated precondition (both tasks in the workspace) is the closest thing to a usage rule.

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