Skip to main content
Glama

Remove team member

team_removeMember
Destructive

Take someone off a team, which takes back the wikis they held only through it. Anyone leaves a team they are on; taking someone else off requires a maintainer of the team or an organization owner. Recorded in the organization's audit log.

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": {
      "slug": "<slug>",
      "userId": "<userId>",
      "org": "<org>"
    },
    "name": "team_removeMember"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgYesslug of the organization whose people, teams and access to use. Required on every call, even when only one organization is listed; a path never names it.
slugYesThe team's slug, as team_list gives it (platform).
userIdYesThe person's user id, as members_list gives it (user_2abc). Never a name or an email.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description goes beyond them by disclosing the cascading consequence (wikis held solely through the team are revoked), the authorization requirements, and that the action is recorded in the organization's audit log. Those are exactly the mutation details an agent needs before calling a destructive tool.

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?

Three short sentences, front-loaded with the action and its effect, then authorization, then the audit trail. No padding or redundant restatement of the name.

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 three-parameter destructive mutation with no output schema, the description covers effect, side effects, permissions, and auditability — everything needed to call it safely. The only unstated edge case (removing a non-member) is minor and does not impede correct invocation.

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 description coverage is 100%, so all three parameters already carry format and derivation guidance (slug from team_list, userId from members_list, org required on every call). The description adds no parameter-level meaning beyond what the schema states, so the baseline of 3 applies.

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 gives a specific verb and resource ('Take someone off a team') plus the consequential effect ('takes back the wikis they held only through it'), which distinguishes it from team_addMember and from the wiki/code removal siblings. An agent knows exactly what operation this performs without opening the 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?

It states the permission split clearly: anyone may remove themselves, but removing another person requires a team maintainer or organization owner. That is real when-to-use/authorization guidance. It does not name a sibling alternative or cover the 'already-absent member' case, so it falls short of explicit routing guidance.

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