Deletes a global role by its slug in Semaphore UI, enabling removal of obsolete or incorrect role definitions when permitted by edition, license, and access.
delete global role. Availability depends on Semaphore edition, license, and permissions; some Community routes return 404 or empty lists. DELETE /roles/{role_slug}.
| Name | Required | Description | Default |
|---|---|---|---|
| role_slug | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavior — edition/license/permission dependence and that some Community routes return 404 or empty lists — which helps an agent interpret failures. It stops short of saying whether deletion is permanent, what happens to users holding the role, or what a success response looks like.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences, front-loaded with the action, with no padding. Slight waste in the opening lowercase restatement of the tool name, but overall tight and readable.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a destructive mutation with no output schema and no parameter documentation, the description leaves key gaps: irreversibility, side effects on role assignments, and how to source the role_slug. The edition-availability caveat is a good start but insufficient for a delete operation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% for the single required role_slug property, so the description must compensate. Beyond the endpoint template implying it is a path segment, it never explains whether the value is a slug or numeric id, its format, or that list_global_roles is the way to obtain it.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb+resource ("delete global role") and pins it to the endpoint DELETE /roles/{role_slug}, which distinguishes it from the many other delete_* siblings. It does not explicitly contrast with delete_project_role or update_global_role, but the name plus endpoint make the target unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this versus alternatives (e.g. delete_project_role, update_global_role) or what prerequisites exist before deletion. The availability note about edition/license/permissions and 404s is environmental context, not usage routing, so an agent still has to infer when this call is appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.