Skip to main content
Glama

Create a Role

create_role

Create 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

NameRequiredDescriptionDefault
nameYesThe Role's name, unique in this Project
mcp_levelNoThe Role's MCP level: "none" (the default), "minimal" or "rich". "full" must be confirmed by a person in the member-access pane
descriptionNoWhat the Role is for
tool_groupsNoThe 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_modeNo"selected" (the default) or "all"
datasource_idsNoUUIDs 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already establish that this is a non-destructive write operation, but the description adds substantial non-obvious behavior: the new Role only reaches granted Requests, request_mode="all" has broad meaning, and restricted invitations produce invitation_eligibility while the Role is still created. It also clarifies that administrator-only invitations remain available and that an unconfirmed Central offer is not the same restriction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, and the later sentences carry relevant behavioral details rather than filler. The invitation-restriction explanation is dense and somewhat opaque, especially the final sentence about an unconfirmed Central offer, but it remains tied to an edge case an agent may need.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter, nested create tool with no output schema, the description covers the creation effect, access scoping, request_mode semantics, and an important result-side invitation_eligibility note. It leaves permissions and some tool_groups implications to the schema, but the key behavioral context is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real semantic guidance beyond the schema by warning that request_mode="all" should be used only when every approved Request is intended. It reinforces a few schema points such as person confirmation for the Full level, but does not add much for the remaining parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: "Create a custom Role." The creation action is unambiguous and distinguishable from get_role, update_role, and list_roles, though it does not explicitly name those siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives useful guidance on when to set request_mode to "all" and explains that restricted seat-taking invitations still allow the Role to be created. However, it does not explicitly compare this tool with sibling alternatives such as update_role or add_role_members, nor does it state required permissions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources