Is your feature request related to a problem? Please describe.
The get_assessment_requirements tool returns individual requirements with a flat count, but no control-level summary. Consumers receiving a catalog with a specific number of controls have no way to quickly understand scope without iterating every control individually. This forces extra tool calls and delays the first question every user asks: "how big is this?"
Describe the solution you'd like
Add control-level summary data to the get_assessment_requirements response. When no controlId filter is provided, include:
- Total number of controls
- Total number of assessment requirements across all controls
- Per-control counts (control ID, title, requirement count)
Example response shape:
{
"catalog": "my-policy",
"summary": {
"total_controls": 14,
"total_requirements": 47
},
"controls": [
{"id": "CTL-AI-003", "title": "Input Validation", "requirement_count": 3},
],
"requirements": [...]
}
When a controlId filter IS provided, include the count for that control alongside the existing requirements list.
Describe alternatives you've considered
- A separate
list_controls tool returning only summary data. Keeps get_assessment_requirements focused but adds a tool.
- A
complypack://catalog/<name>/summary resource instead of a tool response. Simpler but less discoverable since agents already call the tool.
Is your feature request related to a problem? Please describe.
The
get_assessment_requirementstool returns individual requirements with a flat count, but no control-level summary. Consumers receiving a catalog with a specific number of controls have no way to quickly understand scope without iterating every control individually. This forces extra tool calls and delays the first question every user asks: "how big is this?"Describe the solution you'd like
Add control-level summary data to the
get_assessment_requirementsresponse. When nocontrolIdfilter is provided, include:Example response shape:
{ "catalog": "my-policy", "summary": { "total_controls": 14, "total_requirements": 47 }, "controls": [ {"id": "CTL-AI-003", "title": "Input Validation", "requirement_count": 3}, ], "requirements": [...] }When a
controlIdfilter IS provided, include the count for that control alongside the existing requirements list.Describe alternatives you've considered
list_controlstool returning only summary data. Keepsget_assessment_requirementsfocused but adds a tool.complypack://catalog/<name>/summaryresource instead of a tool response. Simpler but less discoverable since agents already call the tool.