Skip to main content
Glama

Remove Team Member

team_remove_member
Destructive

Remove a team member by author ID, optionally scoped to a workspace, to keep project team access current. Requires TEAM_DB_PATH.

Instructions

Remove a member from the team. Requires TEAM_DB_PATH.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "team_remove_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
authorNoThe author ID/username to remove
workspace_idNoOptional workspace isolation identifier (e.g. "alpha"). Do not use numeric project IDs or "workspace" as the key.

Output Schema

NameRequiredDescriptionDefault
codeNoError code (e.g. VALIDATION_ERROR, INTERNAL_ERROR)
errorNoHuman-readable error message
detailsNoAdditional error context
messageNo
successYes
categoryNoError category (validation, query, connection, internal)
suggestionNoSuggested fix for the error
recoverableNoWhether the error is recoverable
aggregated_errorsNoDetails of individual errors in a multi-step operation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv9.1.0
    • removedInput schema / required
      Removed value: -[
      -  "author"
      -]
  2. First observedv9.0.0

TDQS

C2.9/5.0
Behavior2/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 only the TEAM_DB_PATH requirement and says nothing about whether removal is reversible, what happens to entries authored by the removed member, or whether authorization is needed — meaningful gaps for a destructive operation.

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?

Two short sentences with the operation front-loaded and the environment prerequisite second; nothing is wasted. It is terse to the point of under-specification, but that is a completeness issue rather than a verbosity one.

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

Completeness2/5

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

For a destructive, non-idempotent mutation, the description omits the practical consequences of removal and leaves the required-but-optional 'author' parameter unexplained, which could lead an agent to call it with no target. An output schema exists, so return values need not be described, but the operational semantics remain thin.

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 coverage is 100%, and the schema itself documents both the 'author' target and the 'workspace_id' isolation key with formatting caveats. The description adds no meaning beyond that, so the baseline 3 applies. Notably it does not flag that 'author' is effectively required despite required=0.

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 states a specific verb and resource ('Remove a member from the team'), which is unambiguous about the operation. It does not distinguish itself from adjacent siblings such as team_remove_author_alias or team_delete_entry, so an agent must infer the boundary from names alone.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus team_remove_author_alias, team_update_member_role, or team_delete_entry, and no stated preconditions or exclusions. The only usage-adjacent sentence is an environment requirement ('Requires TEAM_DB_PATH'), which is setup rather than selection guidance.

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