Skip to main content
Glama

Coline

Change channel role

set_channel_role
Idempotent

Makes a channel member an admin, or a member again. Needs the channel's owner.

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": {
      "workspace": "<workspace>",
      "channel": "<channel>",
      "userId": "<userId>",
      "role": "<role>"
    },
    "name": "set_channel_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYes
userIdYes
channelYesChannel id (from list_conversations or list_channels) or its slug.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
okYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare idempotent, non-destructive, non-read-only behavior, so the bar is lower. The description adds a genuine permission requirement ('Needs the channel's owner'), but says nothing about edge cases such as whether the target must already be a member or what happens when demoting the last admin.

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?

Two short sentences, front-loaded with the action and followed by the prerequisite. Slightly cryptic phrasing ('a member again') but no waste.

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

Completeness3/5

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

Output schema and annotations cover return shape and safety profile, but for a four-required-parameter mutation the description leaves the userId target semantics and failure modes unexplained, so it is adequate but not complete.

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

Parameters2/5

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

Schema coverage is 50%, with channel and workspace already documented in-schema and role constrained by an enum. The description only obliquely implies 'member' maps to the userId parameter and adds no meaning for userId or the role values beyond what the enum provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb+resource: makes a channel member an admin or back to member. It clearly scopes to channel roles vs. sheet or generic member roles among the siblings, though it doesn't name those alternatives to sharpen the distinction.

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?

States the prerequisite (the caller needs the channel's owner) which gives useful context, but offers no explicit when-to-use/when-not guidance or pointer to alternative role tools (e.g. update_member_role, set_sheet_role) for non-channel scopes.

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.

Resources