Skip to main content
Glama

link

Relate two tasks with a relationship type or remove that relationship to keep dependencies and subtasks accurate.

Instructions

Relate two tasks, or remove the relation.

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": {
      "id": "<id>",
      "other": "<other>",
      "kind": "<kind>"
    },
    "name": "link"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
kindYesid is <kind> other: blocked, blocking, subtask, parenttask, related, precedes, follows, duplicateof, duplicates
otherYes
removeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations at all, the description carries the full disclosure burden and does not meet it. It correctly flags the two mutation modes (create a link vs remove one), but says nothing about idempotency, permission requirements, whether links are directional, or what happens on a conflicting duplicate link. For a write tool with zero annotation coverage, this is a substantial gap.

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?

At eight words it is front-loaded and free of filler, and the dual create/remove modes are packed into one sentence. It is terse to the point of under-specification, but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A four-parameter mutation tool with no annotations, no output schema, and 25% schema coverage needs considerably more description. Key facts an agent needs to call it correctly — the directionality of relations, the meaning of the relation kinds, and how `remove` behaves — are absent.

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?

Schema coverage is only 25%, and only the `kind` enum list is documented structurally. The description implies `id` and `other` are the two tasks being related, which is modest added value, but it never explains the `remove` flag or how `kind` interacts with removal (e.g., must kind be supplied when un-linking).

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 gives a concrete verb and object: 'Relate two tasks' plus the inverse operation 'remove the relation.' That makes clear it is a link/relationship mutation tool rather than a CRUD tool. It stops short of naming the sibling alternatives or saying what kinds of relations exist, but the core purpose is unambiguous.

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 vs when-not guidance and no sibling routing (e.g., it does not say how this differs from save_task). The second clause about removing a relation implies a mode, but the agent is not told when removal is appropriate or what preconditions apply.

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