AI Collaboration MCP Server

reset_task_dependencies

Reset dependencies for tasks blocked by completed or missing tasks to unblock execution and maintain workflow continuity.

Instructions

Reset task dependencies for tasks that are blocked by completed/missing tasks

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "reset_task_dependencies"
  }
}

Input Schema

Name	Required	Description	Default
`taskIds`	No	Task IDs to reset dependencies for (or empty for all blocked tasks)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 12, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It does not disclose whether the operation is destructive, whether it removes all dependencies or just those to completed/missing tasks, or what permissions are required. This lack of detail is a significant gap for a mutation tool.

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, concise sentence that front-loads the purpose. No unnecessary words or repetition.

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

Completeness3/5

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

Given the tool's simplicity (one optional parameter, no output schema, no annotations), the description is adequate but not complete. It lacks details on effects, reversibility, and error conditions, which would be helpful for appropriate use.

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 coverage is 100% as the parameter 'taskIds' already has a description in the schema. The description adds no new meaning beyond what the schema provides, so baseline score of 3 is appropriate.

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 clearly states the tool resets task dependencies specifically for tasks blocked by completed or missing tasks. This distinguishes it from sibling tools like get_task_status or diagnose_tasks which read or analyze rather than modify.

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?

The description implies usage when dependencies are blocked by completed/missing tasks, but does not provide explicit when-not-to-use guidance or mention alternative tools that might be more appropriate.

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