# `TMCP014` search_requirements filtered by category

The user shall be able to filter requirements by category and receive
only requirements belonging to that category.


:::{dropdown} Is a test for
:open: 
:icon: check-circle-fill
:color: primary

[`MCP005` Search and filter requirements](/requirements/MCP005)
:::
:::{dropdown} Automated in
:open: 
:icon: check-circle-fill
:color: success

{fab}`python` [`test_search_by_category`](https://github.com/agagniere/speky/blob/master/tests/test_mcp_server.py#L399)
:::
:::{dropdown} Source
:icon: file-code
:color: info

__Source file__: [`specs/mcp/test_05.yaml`](https://github.com/agagniere/speky/blob/master/specs/mcp/test_05.yaml)

__Loaded from__: [`speky_mcp`](https://github.com/agagniere/speky/blob/master/specs/mcp/mcp.toml)

:::

## Initial state
The expected state is the final state of
[`TMCP003` Initialize the MCP server](/tests/TMCP003)
## Procedure
### Step 1
The client calls `search_requirements` with category `functional`
```json
{
  "id": 2,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "search_requirements",
    "arguments": {"category": "functional"}
  }
}

```
### Step 2
Verify only functional requirements are returned.
RF03 and RF04 (non-functional) must not appear.

```json
{
  "id": 2,
  "jsonrpc": "2.0",
  "result": {
    "structuredContent": {
      "requirements": [
        {"category": "functional", "id": "RF01"},
        {"category": "functional", "id": "RF02", "short": "Second"}
      ]
    }
  }
}

```