Skip to main content
Glama

delete_organization_custom_role

Destructive

Delete a custom gym role (confirm-gated). Owner only. Get explicit confirmation of exactly which role first — members holding it lose its access.

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": "delete_organization_custom_role"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds material context they don't: the owner-only permission requirement and the downstream consequence that members holding the role lose its access. It still doesn't say whether the deletion is reversible or how to recover/recreate the role.

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?

Three short, front-loaded sentences: action, authorization, then the confirmation instruction with its consequence. No filler, though the parenthetical "(confirm-gated)" partially duplicates the opening of the confirmation sentence.

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 3-parameter destructive mutation with annotations present and no output schema, the description covers action, permission, required confirmation flow, and impact. The remaining gap is the undocumented organizationId parameter, which is left entirely to the schema.

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

Parameters3/5

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

Schema coverage is only 33% — roleId and organizationId are undocumented in the schema. The description partially compensates by implying roleId identifies the exact role to delete and flagging the confirm gate, but it never states that confirm must be true to execute (only the schema does) and adds nothing about organizationId.

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?

States a specific verb and resource ("Delete a custom gym role") plus a distinguishing qualifier (confirm-gated). An agent can immediately separate this from create_organization_custom_role, update_organization_custom_role, and list_organization_custom_roles without reading their schemas.

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?

Gives clear preconditions — owner-only authorization and mandatory explicit confirmation of which role before executing. It does not name alternatives or state when-not-to-use (e.g., prefer update to merely revoke permissions), leaving a small gap from a 5.

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.