Skip to main content
Glama
Sign In
@dropthis/mcp

@dropthis/mcp

Official
by dropthis-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Remove a workspace member

dropthis_remove_member
Destructive

Remove a member from a team workspace using workspace ID and account ID, or leave the workspace with your own ID. Requires confirmation.

Instructions

Remove a member from a team workspace by the workspace id and the member's accountId (from dropthis_members), or leave the workspace by passing your own accountId. Destructive; requires confirm: true. Removing others requires a team-scoped credential (ADR-0068: members:admin); leaving needs members:write.

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>",
      "confirm": "<confirm>"
    },
    "name": "dropthis_remove_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true to remove.
workspaceYesThe workspace id (see dropthis_workspaces).
account_idYesThe member's accountId to remove, or your own to leave (see dropthis_members).

Output Schema

NameRequiredDescriptionDefault
removedNo
accountIdNo
workspaceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.37.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the destructiveHint annotation, the description discloses the need for `confirm: true` and details the specific credential scopes (members:admin vs members:write). This adds significant behavioral context about permissions and necessary precautions, exceeding what annotations alone provide.

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 is two sentences and directly front-loads the action. It packs essential details (destructive nature, confirm requirement, credentials, dual use case) without redundancy or verbosity.

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?

The description covers both possible use cases, the destructive nature, the mandatory confirmation, and the credential prerequisites. Given the tool's complexity and the existence of an output schema, this is complete for guiding correct invocation.

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?

The schema already documents all parameters (100% coverage), but the description adds meaningful semantics: it explains that account_id can refer to either another member or yourself for leaving the workspace, and it clarifies the purpose of the confirm flag. This goes beyond the schema's literal field descriptions.

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 action: 'Remove a member from a team workspace by the workspace id and the member's accountId' and explicitly covers the alternative use case of leaving the workspace by passing your own accountId. This distinguishes it from sibling tools like dropthis_update_member_role or dropthis_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 clear context: it says when to use this tool (to remove a member or leave the workspace) and gives prerequisites (credential requirements for each scenario). It doesn't explicitly name alternative tools for the 'when not to use' case, but the distinction between the two allowed actions is strong enough guide.

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

Deploy Server

Other Tools