Tool Reference
atoms_get_coverage
Find requirements without linked test cases
Analyze test coverage across requirements in a project. Identifies requirements that lack linked test cases, helping you find coverage gaps. In capable MCP hosts, this tool renders an interactive coverage heatmap via the MCP App protocol.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
project_id | string (UUID) | Yes | The project to analyze |
domain | string | No | Filter coverage analysis by domain |
level | string | No | Filter coverage analysis by level: System, Subsystem, or Component |
Example Response
{
"status": "success",
"data": {
"covered": 38,
"uncovered": 7,
"total": 45,
"coverage_percent": 84.4,
"uncovered_items": [
{
"id": "REQ-012",
"title": "System shall support offline mode",
"type": "requirement",
"domains": ["reliability"],
"level": "System"
},
{
"id": "REQ-034",
"title": "Data export shall include CSV format",
"type": "requirement",
"domains": ["data"],
"level": "Subsystem"
}
]
}
}Notes
- This tool is read-only and does not modify any data (
readOnlyHint: true). - A requirement is considered "covered" when at least one test case is linked to it via a
verifiesrelationship. - Use the
domainandlevelfilters to analyze coverage for a specific slice of the project, for example allsafety-domain system-level requirements. - The
uncovered_itemsarray lists every requirement that has zero linked test cases, making it straightforward to prioritize test authoring. - In MCP hosts that support the App protocol, this tool displays an interactive coverage heatmap alongside the JSON response.