repair_relationships

Fix task hierarchy and dependency issues.

Repairs Performed:

Resolves circular dependencies
Fixes broken parent-child links
Removes invalid dependencies
Updates status inconsistencies
Corrects metadata anomalies

When to Use:

After failed operations
Fixing circular dependencies
Resolving orphaned tasks
Maintaining task integrity
Before major updates

Best Practices:

Run dry-run first
Fix critical paths
Verify results
Document changes
Update affected tasks
Monitor cascading effects

Validation Steps:

Path integrity check
Dependency cycle detection
Parent-child validation
Status consistency check
Metadata validation

Example: { "dryRun": true, "reasoning": "Checking for relationship issues after recent bulk operations. Using dry-run to assess the scope of necessary repairs before applying fixes." }

Input Schema

Name	Required	Description	Default
`dryRun`	No	Preview changes without applying them. Note: This operation: - Identifies broken relationships - Detects circular dependencies - Finds orphaned tasks - Reports potential fixes
`reasoning`	No	Explanation for repair operation. Best practices: - Document known issues - Note suspected causes - Record repair strategy - Track affected tasks

Input Schema (JSON Schema)

{
  "properties": {
    "dryRun": {
      "default": false,
      "description": "Preview changes without applying them.\nNote: This operation:\n- Identifies broken relationships\n- Detects circular dependencies\n- Finds orphaned tasks\n- Reports potential fixes",
      "type": "boolean"
    },
    "reasoning": {
      "description": "Explanation for repair operation. Best practices:\n- Document known issues\n- Note suspected causes\n- Record repair strategy\n- Track affected tasks",
      "type": "string"
    }
  },
  "type": "object"
}

atlas-mcp-server

repair_relationships

Input Schema

Input Schema (JSON Schema)

Other Tools