past.dev

Change a member's role

set_member_role

DestructiveIdempotent

Changes a member's platform role: Owner, Admin, Member or Billing. Mirrors the Platform role select on Settings › Members; needs Owner or Admin, and only an Owner sets or clears Owner. Making someone Owner transfers ownership: they become the Owner and the person you act for becomes an Admin. A pending invitation cannot become Owner, and the last Owner cannot step down. Destructive: call without confirm first, put the sentence it answers to the person, and pass confirm: true only if they agree.

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": {
      "memberId": "<memberId>",
      "role": "<role>",
      "confirm": "<confirm>"
    },
    "name": "set_member_role"
  }
}

Input Schema

Name	Required	Description
`role`	Yes	Owner, Admin, Member or Billing.
`confirm`	Yes	True only once the person has agreed to the change.
`memberId`	Yes	The member's id, as list_members returns it.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 6, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Far exceeds the annotations: it discloses the ownership-transfer side effect (actor is demoted to Admin), the pending-invite restriction, the last-Owner guard, and an explicit destructive-confirmation protocol tied to the confirm parameter. This is precisely the behavioral context the destructiveHint/idempotentHint flags cannot convey.

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?

Front-loaded with the verb, resource and role set, then escalates to permissions, side effects and the destructive protocol. Dense but every sentence carries a constraint; the role enumeration is mildly redundant with the schema.

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 3-param mutation with no output schema, the description covers prerequisites, ownership side effects, blocked cases and the confirmation workflow. An agent has everything needed to call it safely.

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 100%, so the baseline is 3, but the description adds real meaning for 'confirm' by specifying the two-step flow: call without confirm to obtain the sentence, then pass confirm: true only after the person agrees. The role list merely echoes 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?

States a specific verb ('Changes') and resource ('a member's platform role'), and enumerates the four possible roles. The word 'platform' plus the Settings › Members reference distinguishes it from project-scoped siblings like grant_project_access and from invite_member/remove_member.

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?

Gives clear context: it mirrors the Platform role select on Settings › Members and requires Owner or Admin, with Owner-only for setting/clearing Owner. It states exclusions (pending invitation cannot become Owner; last Owner cannot step down). It stops short of explicitly naming the sibling to use for project-level access instead.

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

All past.dev tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?