Skip to main content
Glama

Remove a group member

remove_group_member
Destructive

An organizer removes a named member from a group. This also removes their entry from hidden-list games still sealing. Requires mcp:manage.

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": {
      "token": "<token>",
      "userId": "<userId>"
    },
    "name": "remove_group_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes
userIdYes
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Pass "unknown" if you are not certain. Recorded for the server developer's analytics.
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the mutation risk is known. The description adds real value beyond that by disclosing a non-obvious side effect — removal from hidden-list games still sealing — and the mcp:manage scope requirement, which an agent could not infer from the schema.

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 sentences, zero filler, with the core action stated first and the side effect and permission requirement trailing in priority order. Nothing is redundant with the title or annotations.

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 destructive membership mutation with no output schema, the definition covers the action, the hidden-list side effect, and the authorization scope. Minor gaps remain around failure behavior and whether the removed member is notified, but an agent has enough to invoke it correctly.

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 50%: llm_model and conversation_id are self-documented, while token and userId carry no schema descriptions. The description indirectly clarifies userId ("a named member") and implies token is the organizer credential via "Requires mcp:manage", but adds no format or lookup guidance for either.

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?

"An organizer removes a named member from a group" gives a specific actor, verb, and resource, which cleanly separates it from self-service siblings like leave_group. It stops short of naming any sibling explicitly, so the contrast is inferred rather than stated.

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?

The phrase "An organizer removes..." implies the caller must hold an organizer role, and "Requires mcp:manage" gives a concrete precondition. However, it never says when to prefer this over moderate_group_member or leave_group, nor what happens when the target is not a member.

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