Skip to main content
Glama
Sign In
coalesce-transform-mcp

coalesce-transform-mcp

Official
by Coalesce-Software-Inc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Delete Env Role

delete_env_role
Destructive

Remove a user's role from an environment, immediately revoking access. Requires explicit confirmation to proceed.

Instructions

Remove a user's role from a specific environment. Destructive — the user will lose environment access immediately.

Args:

  • userID (string, required): The user ID

  • environmentID (string, required): The environment ID

  • confirmed (boolean, optional): Set to true after the user explicitly confirms the role removal

Returns: Confirmation message.

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": {
      "userID": "<userID>",
      "environmentID": "<environmentID>"
    },
    "name": "delete_env_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIDYesThe user ID
confirmedNoSet to true after the user explicitly confirms the role removal.
environmentIDYesThe environment ID

Output Schema

NameRequiredDescriptionDefault
idNo
nameNo
messageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.1

TDQS

A4.2/5.0
Behavior4/5

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

The description discloses that the user loses environment access immediately, which goes beyond the annotation's destructiveHint=true. It also explains the optional 'confirmed' parameter for explicit user confirmation.

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?

The description is brief and well-structured: a one-sentence purpose, a warning, a clear list of arguments, and a return description. No extraneous information.

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?

Given the tool's simplicity (3 parameters, no enums), the description covers the main points: purpose, immediate destructive effect, required and optional parameters, and return type. Could optionally mention that the role must exist, but not necessary for completeness.

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 description coverage is 100%, so the baseline is 3. The description lists the three parameters with types and requiredness, and adds context for 'confirmed' (user confirmation). However, it does not significantly extend beyond the schema's own descriptions.

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?

The description clearly states the action: 'Remove a user's role from a specific environment.' It specifies the resource (role), verb (remove), and context (environment). It is distinct from sibling tools like set_env_role which adds/updates roles.

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?

The description notes that the action is destructive and immediate, implying it should be used only when removal is intended. It does not explicitly list alternatives (e.g., set_role with null), but the clear labeling and sibling context suffice.

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

Deploy Server

Other Tools