Skip to main content
Glama

update_organization_custom_role

Replace a custom role's name, description and capabilities (confirm-gated). Owner only. Sends the full capability list, and changes access for everyone who holds the role.

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": {
      "organizationId": "<organizationId>",
      "roleId": "<roleId>",
      "name": "<name>",
      "capabilities": "<capabilities>"
    },
    "name": "update_organization_custom_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
roleIdYes
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
descriptionNo
capabilitiesYes
organizationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only cover readOnly=false, openWorld=false, destructive=false; the description adds the important operational facts: an owner-level auth requirement, a confirm/preview gate, whole-list replacement semantics, and that the change propagates to every holder of the role. That is exactly the behavior an agent cannot get from the structured fields.

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

Conciseness5/5

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

Three short sentences, front-loaded with the mutation verb and scope, then the permission gate, then the side effect. No filler or restatement of the title.

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 destructive-capable mutation with no output schema, the description covers auth, execution gating and side effects adequately. It stops short of saying what the preview returns or how members currently holding the role are affected if a capability is dropped.

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?

With schema description coverage at 17%, the description must carry the load, and it does the most important part: clarifying that "capabilities" is a full replacement list rather than a patch, and that confirm gates execution. organizationId, roleId and description are still left to the schema, so it is strong but not complete.

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

Purpose5/5

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

A specific verb ("Replace") bound to a specific resource (a custom role's name, description and capabilities), which an agent can distinguish from the create/delete custom-role siblings by resource scope alone.

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

Usage Guidelines4/5

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

States the prerequisite ("Owner only") and the mechanics of the confirm gate, and warns about the blast radius ("changes access for everyone who holds the role"), which is decision-relevant before calling. It does not explicitly contrast with create_organization_custom_role or update_organization_coach_role, so guidance is clear but not fully routing.

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.