@dropthis/mcp

Official

by dropthis-dev

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Change a member's role

dropthis_update_member_role

Idempotent

Update a member's workspace role (owner, admin, member). Set confirm=true to transfer ownership when assigning the owner role.

Instructions

Change a workspace member's role to owner, admin, or member, by the workspace id and the member's accountId (from dropthis_members). Requires a team-scoped credential (ADR-0068: members:admin); only an owner may touch an owner, enforced server-side. Setting role=owner TRANSFERS ownership of the workspace to that member — a high-impact handoff that requires confirm: true.

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>",
      "account_id": "<account_id>",
      "role": "<role>"
    },
    "name": "dropthis_update_member_role"
  }
}

Input Schema

Name	Required	Description
`role`	Yes	The new role: owner (transfers ownership), admin, or member.
`confirm`	No	Must be true to transfer ownership (role=owner). Ignored for admin/member.
`workspace`	Yes	The workspace id (see dropthis_workspaces).
`account_id`	Yes	The member's accountId (see dropthis_members).

Output Schema

Name	Required	Description	Default
`role`	No
`email`	No
`isYou`	No
`joinedAt`	No
`accountId`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.37.0Aug 6, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description goes beyond annotations by disclosing the high-impact side effect: setting role=owner transfers ownership of the workspace, requiring confirm=true. It also mentions the credential requirement and server-side enforcement, adding valuable behavioral context not present in the annotations.

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?

The description is well-structured and front-loaded with the primary action. It uses three informative sentences without redundancy. It could be slightly more compact, but each sentence adds necessary detail for a high-impact operation.

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 tool with 4 parameters, an output schema, and sensitive ownership-transfer behavior, the description covers all critical aspects: purpose, required permissions, ownership transfer semantics, and confirm requirement. It is complete enough for an agent to select and invoke the tool correctly.

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

Parameters5/5

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

Although the schema already covers all parameters (100% coverage), the description enriches meaning by explaining that role=owner is an ownership transfer and that confirm must be true for that case. It also clarifies the source/context for workspace and account_id, improving understanding beyond the schema descriptions alone.

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 states the verb 'Change' with a specific resource 'a workspace member's role' and enumerates the allowed values (owner, admin, member). It also specifies the key identifiers (workspace id and accountId), distinguishing it from sibling tools like remove/invite 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 provides context on when the tool is appropriate by stating the required team-scoped credential (members:admin) and the server-side rule that only an owner may modify an owner. While it doesn't explicitly contrast with alternatives, the constraints and the clear purpose imply correct usage.

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