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

coalesce-transform-mcp

Official
by Coalesce-Software-Inc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Set Env Role

set_env_role
Idempotent

Assign a user role in a specific environment to manage permissions. Idempotent operation ensures consistent, duplicate-free updates.

Instructions

Set a user's role for a specific environment. Idempotent.

Args:

  • userID (string, required): The user ID

  • environmentID (string, required): The environment ID

  • role (string, required): Role to assign

Returns: Updated role assignment.

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>",
      "role": "<role>"
    },
    "name": "set_env_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYesThe environment role to assign (e.g., 'admin', 'developer', 'viewer')
userIDYesThe user ID
environmentIDYesThe environment ID

Output Schema

NameRequiredDescriptionDefault
idNo
nameNo
messageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.1

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already provide idempotentHint=true, destructiveHint=false, and readOnlyHint=false. The description adds 'Idempotent' and mentions the return type ('Updated role assignment'), which provides some additional behavioral context but does not go beyond what annotations already cover in terms of safety profile.

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 extremely concise: a single sentence followed by a brief structured 'Args' section. Every sentence is necessary and front-loaded, with no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple three-parameter idempotent mutation tool with full schema coverage and output schema, the description provides all necessary context. It covers purpose, parameters, and return value adequately.

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 100%, so the schema already describes all three parameters adequately. The description lists the parameters in a concise 'Args' section, but this adds little beyond the schema descriptions (e.g., role description already gives examples).

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 'Set a user's role for a specific environment.' It uses a specific verb+resource and implicitly differentiates from siblings like delete_env_role, set_org_role, and set_project_role by specifying the scope (environment).

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?

The description indicates the tool is for assigning a role to a user for an environment, but it does not explicitly state when to use this tool over alternatives (e.g., set_org_role, set_project_role) or provide any exclusions or prerequisites. The usage context is implied rather than explicit.

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