atoms_trace

Walk the traceability graph from a starting item, following relationships upstream, downstream, or both directions. In capable MCP hosts, this tool renders an interactive MCP App with a force-directed graph visualization for exploring traceability chains.

Parameters

Example Response

{
  "status": "success",
  "data": {
    "root": "REQ-005",
    "direction": "both",
    "items": [
      {
        "id": "REQ-001",
        "title": "System shall maintain audit trail",
        "type": "requirement",
        "relationship": "parent",
        "depth": 1
      },
      {
        "id": "TC-020",
        "title": "Verify audit entries on data modification",
        "type": "test-case",
        "relationship": "verifies",
        "depth": 1
      },
      {
        "id": "REQ-010",
        "title": "Audit log retention policy",
        "type": "requirement",
        "relationship": "child",
        "depth": 2
      }
    ],
    "total_count": 3
  }
}

Notes

• This tool is read-only and does not modify any data (readOnlyHint: true).
• Upstream follows parent and verifies relationships : showing what the starting item depends on.
• Downstream follows child and verified_by relationships : showing what depends on the starting item.
• A maximum of 200 items is returned per call. For highly connected graphs, use depth or relationship_types to narrow the scope.
• Use relationship_types to filter the traversal. For example, pass ["verifies", "verified_by"] to trace only the testing chain without parent/child structural links.