Skip to main content
Glama

Remove a member

remove_member
Destructive

Remove a membership, revoking that person's workspace access. Workspace owners only.

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_id": "<workspace_id>",
      "membership_id": "<membership_id>"
    },
    "name": "remove_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idYesThe workspace id (from whoami).
membership_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered. The description adds genuine extra context by naming the concrete consequence (workspace access is revoked) and the owner-only permission requirement. It omits reversibility (can the person be re-invited, does prior content persist) and any failure behavior, so it is not a full 5.

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?

Two short sentences with no filler, and the effect statement leads ahead of the permission constraint. Every clause carries information an agent needs.

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

Completeness3/5

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

For a two-parameter destructive tool with no output schema, the description covers the effect and the authorization requirement, which is enough to avoid the most damaging mistakes. It is still incomplete on how to source membership_id and on what the caller receives or should expect on failure, which matters given the destructive annotation.

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

Parameters2/5

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

Schema description coverage is only 50%: workspace_id is documented as coming from whoami, but membership_id has no description anywhere. The description does not explain how to obtain a membership_id (presumably via list_members) or what happens if the id refers to an owner, so it fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ("Remove a membership") and states the effect ("revoking that person's workspace access"), so an agent can tell it apart from invite-related or leave_workspace operations. It stops short of naming an explicit sibling alternative, which keeps it at 4 rather than 5.

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

Usage Guidelines3/5

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

"Workspace owners only" supplies a clear authorization precondition for when this call can succeed. However, there is no guidance on when to prefer this over adjacent operations such as revoke_invite or set_member_role, and no note on what to do when the caller is not an owner.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources