list_requirements
A project's functional and non-functional requirements in the project's order, with reference, kind, category, statement, source, priority, measure, verification method, status and owner, narrowed for a guest token.
Return the requirements of one project: what the system shall do (functional, CRM-FR-12) and the qualities it shall keep (non-functional, CRM-NFR-3, each with the category it belongs to and the measure that says when it is met), each with its statement, rationale, where it came from (a stakeholder of the project, or words), MoSCoW priority, how it will be shown to be met, status and owner. Read it before you design, build or test, so the behaviour the client agreed and the qualities it is held to are in front of you, and name requirements by their reference when you report.
Optional filters narrow the page to one type, one category, one status, one priority, one owner_id or the requirements whose reference, title or source contain search. A guest token reads the agreed requirements only (approved or baselined).
Requires ability
The token behind the MCP session must hold it, or the call is refused with TOKEN_MISSING_ABILITY.
Runs the same action as
The REST endpoint and this tool share one action, so validation, permissions and events are identical.
Annotations
It reads and never changes anything.
Arguments
project_id*stringUUID of the project whose requirements to list.
typestringoptionalNarrow to one kind.
functionalnon_functionalcategorystringoptionalNarrow to the non-functional requirements of one category.
performancescalabilityavailabilityreliabilitysecurityprivacyusabilityaccessibilitycompatibilitymaintainabilityportabilitycomplianceobservabilitylocalisationotherstatusstringoptionalNarrow to one status.
draftin_reviewapprovedbaselineddeprecatedprioritystringoptionalNarrow to one MoSCoW priority.
mustshouldcouldwontowner_idstringoptionalNarrow to the requirements one person answers for, by user UUID.
searchstringoptionalWords the reference, the title or the source must contain.
limitintegeroptionalRequirements per page (1..100, default 25).
1max100pageintegeroptional1-indexed page number.
1What it returns
{ "data": [ { "id": "c4d5e6f7-a8b9-4c0d-9e1f-2a3b4c5d6e7f", "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13", "type": "non_functional", "number": 3, "reference": "CRM-NFR-3", "category": "performance", "title": "Tier page answers within a third of a second", "statement": "<p>The system shall render a member's tier page within 300 ms at the 95th percentile with 500 members browsing at once.</p>", "rationale": null, "source_stakeholder_id": "d6e7f8a9-b0c1-4d2e-9f3a-4b5c6d7e8f90", "source_stakeholder_name": "Amal Jayasuriya", "source": "Discovery workshop, 14 October", "priority": "must", "measure": "p95 under 300 ms at 500 concurrent users, measured on staging", "verification_method": "test", "status": "approved", "owner_id": "c3d4e5f6-a7b8-4c9d-8e0f-1a2b3c4d5e6f", "owner_name": "Nimal Fernando", "position": 2, "version": 0, "approved_at": "2026-11-05T15:00:00+00:00", "approved_revision_id": null, "created_at": "2026-10-28T09:20:00+00:00", "updated_at": "2026-11-05T15:00:00+00:00" } ], "meta": { "page": 1, "limit": 25, "total": 1, "has_more": false }}How it fails
RESOURCE_NOT_FOUNDunknown project_id, or a project outside the token's scope or the person's visibility.
VALIDATION_FAILEDtype, category, status or priority is not one of its values.
TOKEN_MISSING_ABILITYtoken lacks requirement:view-any.
How is this guide?
Last updated on