Create a Role
create_roleCreate a custom Role. A new Role reaches only the Requests granted to it, directly or through shared apps; set request_mode to "all" only when you mean every approved Request. When seat-taking invitations are restricted, the result carries invitation_eligibility, the same note list_users reports, including upgrade_url, and the Role is still created. The note is about inviting a new person; Administrator-only invitations stay available. An offer Central did not confirm is not that restriction.
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": {
"name": "<name>"
},
"name": "create_role"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | The Role's name, unique in this Project | |
| mcp_level | No | The Role's MCP level: "none" (the default), "minimal" or "rich". "full" must be confirmed by a person in the member-access pane | |
| description | No | What the Role is for | |
| tool_groups | No | The Role's tool toggles, as an object of toggle names to booleans (addQueryManagement, addDataChangingRequests, addSchemaGovernance, addDatasourceManagement, addOntologyMaintenanceTools, addOntologySuggestions, addWorkflowTools, addWorkflowParticipation). The Administrator Role's toggles are the Project's grants; any other Role uses only the member-facing one (addWorkflowParticipation). | |
| request_mode | No | "selected" (the default) or "all" | |
| datasource_ids | No | UUIDs of the datasources this Role's Rich or Full level applies to. Omitted leaves the list unchanged. Rich and Full need at least one. Adding a datasource to Full must be confirmed by a person. |