Skip to main content
Glama

Update a Role

update_role
Idempotent

Change a Role. Omitted fields keep their values. Built-in Roles keep their names and descriptions. Administrator always reaches every approved Request; Member and End users may select Requests. End users has no members. The Administrator Role's toggles are the Project's grants, and changing one is recorded.

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": {
      "role_id": "<role_id>"
    },
    "name": "update_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoA new name
role_idYesUUID of the Role
mcp_levelNoThe Role's MCP level: "none", "minimal" or "rich"; omitted preserves the current value. "full" must be confirmed by a person in the member-access pane
descriptionNoA new description
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). Pass the complete set: omitted toggles are turned off.
request_modeNo"all" or "selected"
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; removing one does not.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (which already say non-destructive, idempotent, closed-world), the description adds real behavioral context: patch semantics for omitted fields, that built-in Roles have immutable names/descriptions, and that changes to the Administrator Role's toggles are recorded as Project grants. It omits error/permission failure behavior, but the disclosure is well above what the annotations carry.

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

Conciseness3/5

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

The sentences are short and front-loaded, but several ("Administrator always reaches every approved Request; Member and End users may select Requests. End users has no members.") are terse to the point of being cryptic and only loosely tied to invoking this tool, so signal is diluted.

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 7-parameter mutation with a nested toggle object and no output schema, the description covers the critical semantics: partial-update behavior, immutable built-in Roles, and the special Administrator-as-Project-grants meaning. Missing pieces such as name uniqueness or permission requirements are minor given the fully documented schema.

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. The description goes beyond it by framing role-type constraints that govern which fields are meaningful — built-in Roles for name/description, Administrator vs. Member/End-user toggles — which helps the agent avoid invalid combinations the schema alone does not prevent.

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?

"Change a Role" names a concrete verb and resource, and the surrounding sentences make clear this is a field-level patch on an existing role rather than a create/delete. It does not explicitly name siblings like create_role or set_role_requests, so differentiation is implied rather than stated.

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?

"Omitted fields keep their values" tells the agent this is a partial update, which is the key usage signal. However, it never says when to prefer this tool over create_role, set_role_requests, or add_role_members, and the role-behavior sentences read as domain reference notes rather than routing guidance.

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