atoms_project_summary

Retrieve a comprehensive health and compliance dashboard for an entire project in a single call. Returns item counts, test status breakdowns, coverage metrics, and recent changes. In capable MCP hosts, this tool renders an interactive MCP App with charts and gauges for visual project oversight.

Parameters

Example Response

{
  "status": "success",
  "data": {
    "project_id": "6f1d0c52-8d5e-4b8e-9d55-0d6f5a1c2b3e",
    "project_name": "Drive Pilot v2",
    "counts": {
      "requirements": 48,
      "test_cases": 35,
      "notes": 12
    },
    "test_status": {
      "passed": 22,
      "failed": 5,
      "blocked": 3,
      "not_run": 5
    },
    "coverage": {
      "covered": 38,
      "uncovered": 10,
      "total": 48,
      "percent": 79.2
    },
    "coverage_by_domain": [
      { "domain": "performance", "covered": 5, "total": 8, "percent": 62.5 },
      { "domain": "safety", "covered": 12, "total": 14, "percent": 85.7 },
      { "domain": "security", "covered": 8, "total": 10, "percent": 80.0 }
    ],
    "recent_changes": 14,
    "last_updated": "2025-04-12T16:45:00.000Z"
  }
}

Notes

• This tool is read-only and does not modify any data (readOnlyHint: true).
• This is the most efficient way to get an overview of project health: a single call returns what would otherwise require multiple queries across atoms_list_items, atoms_get_coverage, and atoms_get_history.
• test_status counts every live test case exactly once, by its latest result. A test case with no result, or whose latest result is not-run, counts as not_run, so the four counts add up to counts.test_cases.
• coverage is link based: a requirement is covered when it has a verified_by or verifies link, and percent is covered over total (100 when the project has no requirements). It is not the Coverage column of the web app's Matrix, which counts live test cases only and rolls up over child requirements, and it says nothing about whether the linked tests passed. Use atoms_verification_status for the verification state of each requirement.
• coverage_by_domain breaks the same numbers down by domain tag (requirements without a domain are listed as (untagged)), sorted by domain name, which helps prioritize testing effort.
• recent_changes is the number of changes recorded in the last 7 days, not a list.