Skip to main content
Glama

Change a member's role

company_member_role_set
Idempotent

Changes the role of another member of one of your companies. Owners can change any role; admins only between member and viewer. You cannot change your own role and a company keeps at least one owner. Call without confirm first for a preview, then again with confirm and the preview_token.

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": {
      "company": "<company>",
      "member": "<member>",
      "role": "<role>"
    },
    "name": "company_member_role_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYes
memberYesMember ref (MB-XXXXXXXX) from company_members_list.
companyYesCompany ref (CO-XXXXXXXX) from company_list_mine.
confirmNoSet true only on the second call, after the user approved the preview.
preview_tokenNoThe preview_token returned by the first call (same input).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations it discloses the authorization model, two hard invariants (no self-role change, at least one owner must remain), and the preview/confirm handshake. These are exactly the behavioral facts an agent cannot derive from readOnlyHint=false, idempotentHint=true, or destructiveHint=false.

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?

Three short sentences ordered from purpose to constraints to call sequence, with no filler. Each sentence carries information the agent needs before invoking.

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 five-parameter mutation with no output schema, the definition covers scope, permissions, invariants, and the required two-call flow. Nothing essential for a correct invocation is missing.

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

Parameters4/5

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

Schema coverage is already 80%, including ref patterns, the role enum, and per-parameter descriptions; the description adds the meaning of the confirm/preview_token pairing as a two-call sequence. That is meaningful context above the schema, though it does not restate ref formats.

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?

The description uses a specific verb and resource ('Changes the role of another member of one of your companies') and scopes it with 'another member' and 'you cannot change your own role', which separates it in practice from removal-oriented siblings like company_member_remove. It stops short of explicitly naming an alternative tool, so it is clear but not fully sibling-differentiated.

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?

Strong operational guidance: it states the two-step protocol (call without confirm for a preview, then again with confirm and the preview_token) and the permission tiers (owners any role, admins only member/viewer). It does not point to sibling alternatives for related tasks such as removal or invitation, which keeps it 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.

Resources