Skip to main content
Glama
Sign In
Taskmaster

Taskmaster

by eyaltoledano
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

remove_dependency

Remove task dependencies to simplify workflows in AI-driven development. Specify task IDs and project paths to eliminate unnecessary dependencies, ensuring cleaner task management in the Task Master system.

Instructions

Remove a dependency from a task

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>",
      "dependsOn": "<dependsOn>",
      "projectRoot": "<projectRoot>"
    },
    "name": "remove_dependency"
  }
}

Input Schema

NameRequiredDescriptionDefault
dependsOnYesTask ID to remove as a dependency
fileNoAbsolute path to the tasks file (default: tasks/tasks.json)
idYesTask ID to remove dependency from
projectRootYesThe directory of the project. Must be an absolute path.
tagNoTag context to operate on

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Remove a dependency' implies a mutation operation, but the description doesn't specify whether this requires specific permissions, whether the change is reversible, what happens to dependent tasks, or what the response looks like. For a mutation tool with zero annotation coverage, this represents a significant gap in behavioral transparency.

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 a single, efficient sentence that communicates the core purpose without unnecessary words. It's appropriately sized for a tool with this level of complexity and gets straight to the point with zero wasted verbiage.

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?

For a mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what happens after dependency removal, whether there are side effects on other tasks, what success/failure looks like, or how this interacts with sibling dependency management tools. The description should provide more context given the tool's complexity and lack of structured metadata.

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%, so the schema already documents all 5 parameters thoroughly. The description adds no additional parameter information beyond what's in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no parameter information in the description.

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 clearly states the action ('Remove') and target ('a dependency from a task'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'remove_subtask' or 'remove_task', which would require more specific language about what distinguishes dependency removal from other removal operations.

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?

The description provides no guidance about when to use this tool versus alternatives. With sibling tools like 'fix_dependencies' and 'validate_dependencies' available, there's no indication of whether this tool is for manual dependency correction versus automated fixes, or any prerequisites for its use.

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

Deploy Server

Other Tools

Related Tools