Skip to main content
Glama

remove_dependency

Destructive

Remove dependency edges linking two tasks. Clear stray or reversed blocks that block task progression and provide a reason for the removal.

Instructions

Remove a dependency edge: task_id (the blocked card) no longer depends on depends_on_task_id. Clears a stray or reversed blocks link that holds a card open. Direction matters: the pair is given in the order add_dependency took it. reason is required and logged.

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": {
      "task_id": "<task_id>",
      "depends_on_task_id": "<depends_on_task_id>",
      "reason": "<reason>"
    },
    "name": "remove_dependency"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYesWhy the link is removed (min 10 chars); written to the server log.
task_idYesThe blocked task (the one that has the dependency).
depends_on_task_idYesThe blocker the edge points at.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description adds non-obvious behavior: the pair must be supplied in the same order add_dependency used, and a mandatory reason string is written to the server log, which signals an audited mutation. It does not say what happens when the edge does not exist or whether the removal is reversible.

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?

Three tight sentences: what it does, why you'd call it, then the ordering and logging constraints. No restatement of the name, no filler, constraints front-loaded where they matter.

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 three-parameter destructive mutation with no output schema and full schema coverage, the description covers purpose, direction, and audit behavior adequately. The remaining gap is edge-case behavior — whether a missing edge is an error or a no-op — which matters given idempotentHint=false.

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, but the description genuinely adds semantics: it clarifies the direction of the edge and that the argument order must mirror add_dependency, which the schema alone does not convey. It also confirms the reason parameter is required and logged, consistent with the schema's min-10-chars note.

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 ('Remove a dependency edge') and immediately names the two identifiers and their roles (blocked card vs. blocker). It is clearly distinguishable from add_dependency and update_dependency, which the direction/order note reinforces.

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?

Gives a concrete use case — clearing a stray or reversed blocks link that holds a card open — which tells the agent when this tool is appropriate rather than add_dependency or update_dependency. It stops short of an explicit exclusion rule (e.g., 'use update_dependency when the edge direction itself is correct but the target changes').

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