role_data_matrix
Run the same OData read with different credentials to verify per-role access and record count. Valid only for separately published, non-exclusive endpoints.
Instructions
DEPRECATED for a test-client-held base — a «Клиент тестирования» holds the infobase under an EXCLUSIVE lock, so OData cannot read it; this matrix is valid only against a SEPARATELY published, non-exclusive endpoint. Run the SAME data-layer read under several credentials/ROLES and report per-role access + count. Each role = {label, user, password} + optional expectation {expect_access: "read"|"denied", min_count: N}. Returns {ok, roles: [{label, access ('read'|'denied'|'error'), count, http, ok}], deprecated, deprecation}. NOTE: a genuine role-DIFFERENCE matrix needs restricted infobase users provisioned out-of-band (admin-mcp) — outside qa-mcp's read-only scope.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"entity_set": "<entity_set>",
"roles": "<roles>"
},
"name": "role_data_matrix"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| roles | Yes | ||
| filter | No | ||
| base_url | No | ||
| entity_set | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||