Skip to main content
Glama

Remove someone from the team

remove_member
DestructiveIdempotent

Removes a team member (list_members): they lose access at once, and the API keys they created here stop working. It first needs a manager's OK in Shager: the call answers needs_confirmation with confirm_url; after they approve, make the same call again. The owner can't be removed, nobody removes themselves this way, and the last full manager stays. (Not available in an unclaimed sandbox.)

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": {
      "member_id": "<member_id>"
    },
    "name": "remove_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
member_idYesFrom list_members
confirmation_tokenNoThe confirmation_token from needs_confirmation. The call goes through only after your human approved this exact action at confirm_url.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations (destructiveHint=true, idempotentHint=true) by disclosing consequences: access is lost at once and API keys the member created stop working. It also documents the two-step approval flow (needs_confirmation → confirm_url → repeat call), which is the non-obvious behavior an agent must handle.

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-loads the action and its consequences, then the confirmation procedure, then the exceptions. It is dense with parentheticals in one long paragraph, but nearly every clause carries decision-relevant information.

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 destructive two-step mutation with no output schema, the description covers side effects, approval mechanics, eligibility restrictions, and environment limits. An agent has everything needed to call it correctly and to know when it will refuse.

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: the confirmation_token only exists after a human approves at confirm_url, and the call is retried unchanged. That explains the sequencing that the schema's field text only hints at.

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 and resource ('Removes a team member') and points at list_members as the source of the member_id, so an agent can distinguish it from role-change or invitation-cancel siblings without opening a schema.

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 a clear when-to-use path and strong exclusions: the owner can't be removed, nobody removes themselves this way, the last full manager stays, and it is unavailable in an unclaimed sandbox. It does not name an alternative tool for downgrading instead of removing, but the negative conditions cover the main misuse cases.

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