Planning System MCP Server

update_member_role

Change a member's role in an organization. Requires owner privileges and prevents demoting the last admin.

Instructions

Change a member's role within an organization. Caller must be org owner. Server rejects demoting the last admin.

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": {
      "organization_id": "<organization_id>",
      "membership_id": "<membership_id>",
      "new_role": "<new_role>"
    },
    "name": "update_member_role"
  }
}

Input Schema

Name	Required	Description
`organization_id`	Yes
`membership_id`	Yes	Membership row id (from listMembers).
`new_role`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.8.1Apr 29, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries full burden. It discloses key behavioral traits: required permission level and a rejection condition for last admin. This adequately informs the agent of critical constraints, though minor details like idempotency or immediate effect are omitted.

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 description consists of two concise sentences with no redundancy. Every sentence adds value: first states purpose, second gives critical constraints.

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

Completeness4/5

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

Given the tool's simplicity (3 parameters, no output schema), the description covers core functionality and key restrictions. It does not mention any additional details like reversibility or side effects, but these are not essential for basic usage.

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 only 33% (membership_id has a description). The description adds no further parameter-specific details beyond the schema. It provides overall context about the caller requirement, but does not elaborate on organization_id or new_role parameters.

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 explicitly states 'Change a member's role within an organization,' providing a clear verb+resource combination. It further clarifies constraints, distinguishing it from sibling tools like invite_member or 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?

The description specifies when to use the tool and includes important prerequisites (caller must be org owner) and conditions (server rejects demoting last admin). While it does not explicitly list when not to use, the context of sibling tools makes it clear.

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