Casefile

Overview Schema Source Related Servers Discussions Admin

unlink

Removes a link between two tasks, accepting either side of the relationship. On closed tasks, deletes 'relates' links only; 'parent' and 'blocks' remain.

Instructions

Removes a link and files link_removed in both cases.

A link is removed from either side and under either name of its kind: blocks from TRK-1 to TRK-7 and blocked_by from TRK-7 to TRK-1 are the same link. On a closed task parent and blocks stay (task_closed), relates is removed. A link that does not exist is refused with link_not_found.

Input Schema

TableJSON Schema

Name	Required	Description
`key`	Yes	Task key `PROJECT-N`, case-insensitive; a previous key of a moved task addresses it as well. An unknown key is refused with `task_not_found`
`kind`	Yes	Role of the task `key` toward the task `other`: `link(key='TRK-1', kind='blocks', other='TRK-7')` means TRK-1 blocks TRK-7, and the card of TRK-7 shows the same link as `blocked_by`
`other`	Yes	Key of the task on the other side of the link

Output Schema

TableJSON Schema

Name	Required	Description
`key`	Yes
`entry`	Yes	Number of the `link_added` or `link_removed` entry in the case of `key`
`other_entry`	Yes	Number of the same entry in the case of `other`

Schema Changelog

Changes observed during successful MCP inspections.

Changed17 schema fields changedv0.5.2Sep 25, 2026

removedInput schema / $defs

Removed value: -{
-  "LinkKind": {
-    "description": "Вид связи. Перечислены обе стороны каждой пары: клиент адресует любую из них.",
-    "enum": [
-      "parent",
-      "child",
-      "blocks",
-      "blocked_by",
-      "relates"
-    ],
-    "title": "LinkKind",
-    "type": "string"
-  }
-}

changedInput schema / properties / key / description

Previous value: -"Ключ задачи, например `TRK-42`. Регистр не важен"New value: +"Task key `PROJECT-N`, case-insensitive; a previous key of a moved task addresses it as well. An unknown key is refused with `task_not_found`"

removedInput schema / properties / kind / $ref
```
Removed value: -"#/$defs/LinkKind"
```

changedInput schema / properties / kind / description

Previous value: -"Кем приходится задача из `key` задаче из `other`, а не наоборот: `link(key='TRK-1', kind='blocks', other='TRK-7')` — это «TRK-1 блокирует TRK-7». В карточке TRK-7 та же связь показана как `blocked_by TRK-1`"New value: +"Role of the task `key` toward the task `other`: `link(key='TRK-1', kind='blocks', other='TRK-7')` means TRK-1 blocks TRK-7, and the card of TRK-7 shows the same link as `blocked_by`"

addedInput schema / properties / kind / enum

Added value: +[
+  "parent",
+  "child",
+  "blocks",
+  "blocked_by",
+  "relates"
+]

removedInput schema / properties / kind / examples
```
Removed value: -[
-  "blocked_by"
-]
```
addedInput schema / properties / kind / type
```
Added value: +"string"
```

changedInput schema / properties / other / description

Previous value: -"Ключ задачи на другой стороне связи"New value: +"Key of the task on the other side of the link"

removedOutput schema / $defs

Removed value: -{
-  "LinkKind": {
-    "description": "Вид связи. Перечислены обе стороны каждой пары: клиент адресует любую из них.",
-    "enum": [
-      "parent",
-      "child",
-      "blocks",
-      "blocked_by",
-      "relates"
-    ],
-    "title": "LinkKind",
-    "type": "string"
-  }
-}

changedOutput schema / description

Previous value: -"Ответ `unlink`: какая связь снята и с какой стороны её назвали."New value: +"Entries filed by `link` or `unlink` on both sides of the link."

addedOutput schema / properties / entry

Added value: +{
+  "description": "Number of the `link_added` or `link_removed` entry in the case of `key`",
+  "title": "Entry",
+  "type": "integer"
+}

removedOutput schema / properties / kind

Removed value: -{
-  "$ref": "#/$defs/LinkKind"
-}

removedOutput schema / properties / other

Removed value: -{
-  "title": "Other",
-  "type": "string"
-}

addedOutput schema / properties / other_entry

Added value: +{
+  "description": "Number of the same entry in the case of `other`",
+  "title": "Other Entry",
+  "type": "integer"
+}

removedOutput schema / properties / removed

Removed value: -{
-  "title": "Removed",
-  "type": "boolean"
-}

changedOutput schema / required

Previous value: -[
-  "key",
-  "kind",
-  "other",
-  "removed"
-]New value: +[
+  "key",
+  "entry",
+  "other_entry"
+]

changedOutput schema / title

Previous value: -"UnlinkView"New value: +"LinkFilingView"

First observedSep 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations are all false and provide no safety or idempotency context, so the description carries the full behavioral burden. It discloses the success event (`link_removed`), symmetric matching from either side, closed-task exceptions (`parent`/`blocks` stay, `relates` removed), and the failure response (`link_not_found`). This is substantial and honest disclosure.

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 three dense sentences with no filler. The first sentence states the action and observed outcome, and the next two handle symmetric matching and important exceptions. Every sentence earns its place.

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?

For a mutation tool with an output schema, this description covers the main success path, a key closed-task behavior, and the primary error case. Minor gaps remain, such as explicit closed-task behavior for `child` and `blocked_by` and any permission requirements, but an agent can still call the tool correctly with high confidence.

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?

Schema coverage is 100%, so the baseline is 3. The description adds semantic value by explaining that `blocks` and `blocked_by` describe the same underlying link and that direction matters relative to `key`/`other`. This goes beyond the schema's field descriptions, though the schema already documents the core parameter roles.

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 states a specific verb and resource: 'Removes a link'. It distinguishes itself from the sibling `link` (which presumably creates links) by describing removal and even notes the symmetric `blocks`/`blocked_by` naming. The core purpose is immediately clear and unambiguous.

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?

The description gives a clear context for when to call the tool: whenever a link should be removed. It covers edge cases like closed tasks and missing links, but it does not explicitly name alternatives or provide an exclusion like 'use link to create a link instead'. This is clear context without full alternative routing, so a 4 fits.

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