Skip to main content
Glama

Coline

Remove someone from a team

remove_team_member
DestructiveIdempotent

Removes someone from a team; they stay in the workspace. People may remove themselves.

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>",
      "teamId": "<teamId>",
      "userId": "<userId>"
    },
    "name": "remove_team_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamIdYesTeam id from list_teams.
userIdYesThe person's user id (userId from list_members).
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
removedYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds two things beyond them: the user is only detached from the team and retains workspace access, and self-removal is permitted — both genuinely useful for judging consequences and authorization. It omits whether admin privileges are needed and what happens to team resources the person belonged to.

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?

A single compact sentence with the scope constraint front-loaded and a secondary eligibility clause tacked on. Every clause carries information; there is no filler or restatement of the title.

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

Completeness4/5

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

For a simple three-parameter destructive tool with full schema coverage and an output schema, the description covers purpose, blast radius, and self-removal eligibility. The remaining gap is prerequisite/authorization detail and side effects on related team objects, which is minor given what annotations and schema already supply.

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% and all three parameters carry descriptions that even point at the source tools (list_teams, list_members). The description adds no parameter-level meaning beyond the schema, so the baseline of 3 applies.

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 gives a specific verb and resource ("Removes someone from a team") and immediately scopes the blast radius with "they stay in the workspace," which distinguishes it from workspace-level removal siblings such as remove_member. It stops short of naming an alternative tool explicitly, so an agent must infer the boundary rather than read it.

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?

"People may remove themselves" is a useful eligibility hint, but there is no explicit when-to-use or when-not-to-use guidance relative to remove_member, remove_channel_member, or update_team_member_role. The workspace-versus-team distinction implies the correct context, which is why this lands at implied rather than explicit 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