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

coalesce-transform-mcp

Official
by Coalesce-Software-Inc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Set Org Role

set_org_role
Idempotent

Set a user's organization role (admin, member, viewer) with an idempotent call that can be safely repeated.

Instructions

Set the organization-level role for a user. Idempotent — safe to call multiple times.

Args:

  • userID (string, required): The user ID

  • role (string, required): Role to assign (e.g., 'admin', 'member', 'viewer')

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

Input Schema

NameRequiredDescriptionDefault
roleYesThe organization role to assign (e.g., 'admin', 'member', 'viewer')
userIDYesThe user ID

Output Schema

NameRequiredDescriptionDefault
idNo
nameNo
messageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.1

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true and destructiveHint=false. Description echoes idempotence but adds no new behavioral context such as permission requirements or side effects.

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?

Short and front-loaded with purpose and key trait (idempotent). Could benefit from bullet parameter list but remains efficient.

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, two-parameter tool with output schema present, the description covers purpose, idempotence, and return value fully. No gaps.

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 baseline 3. Description merely restates parameter descriptions with example role values, adding minimal additional meaning beyond the schema.

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?

Clearly states verb 'set' and resource 'organization-level role', and title reinforces. Distinguishes from sibling tools like set_env_role and set_project_role.

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?

Mentions idempotence, implying safe repeated calls, but does not explicitly contrast with alternative tools or provide when-to-use guidance. Name and description suffice for purpose-driven selection.

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