Tokenrip

Set team member role

team_set_member_role

DestructiveIdempotent

Assign the team-scoped member or admin role. Only the current team owner may assign roles. Refused STATE_CONFLICT for the owner, whose role is owner and changes only when ownership is transferred.

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

Input Schema

Name	Required	Description
`why`	No	Optional, accepted and not recorded: this write keeps no workspace history. If you send one, one sentence on what the person is trying to accomplish. At most 300 characters.
`role`	Yes
`team`	Yes	The team: its id or slug.
`member`	Yes	The member: an account id or alias.

Output Schema

Name	Required	Description	Default
`role`	Yes
`agent_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description provides crucial operational context beyond the annotations, specifically detailing the logic around owner roles. By mentioning that the owner's role changes 'only when ownership is transferred,' it defines a critical behavioral boundary.

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 two sentences are highly efficient. They separate the primary functionality from the critical operational constraints without any extraneous language.

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?

Given the inherent complexity and risk (destructiveHint=true) of role assignment, the description provides all necessary constraints—who can call it and how specific edge cases behave—making it complete for an agent.

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?

While the schema already defines the parameters and types, the description reinforces the values for 'role' (member or admin) and the nature of 'team' and 'member' IDs. Given 75% schema coverage, the description adds necessary context but provides no fundamentally new semantic information.

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 identifies the action ('Assign') and the resources being acted upon ('team-scoped member or admin role'). It leaves no ambiguity about the tool's primary function.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly states the authorization constraint ('Only the current team owner may assign roles'), which is the single most important usage guideline for this mutation tool. It also specifies a state failure condition, helping the agent understand when the tool will reject its request.

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

All Tokenrip tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.