Skip to main content
Glama

Approve or decline a group request

moderate_group_member
Destructive

A group organizer accepts or declines a membership request. Use the pending member’s id from get_my_group. 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>",
      "accept": "<accept>"
    },
    "name": "moderate_group_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes
acceptYes
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.5/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is largely covered. The description adds the required permission scope, but it does not explain the consequences of declining, whether the action is reversible, or what the response contains.

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?

The definition is two short sentences that are front-loaded with the core action and free of unnecessary wording. Every sentence adds either purpose, parameter sourcing, or permission context.

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

Completeness3/5

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

For a destructive, open-world mutation with five parameters and no output schema, the description provides only minimal operational context. It covers the core action, id source, and permission requirement, but omits token semantics and the effects of accepting versus declining.

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?

The description clarifies the userId parameter by saying to use the pending member's id from get_my_group, and the accept/decline wording gives meaning to the required boolean. However, the required token parameter is not explained beyond the permission requirement, leaving part of the low schema coverage uncompensated.

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: a group organizer "accepts or declines a membership request." This clearly identifies the operation, though it does not explicitly differentiate it from siblings like remove_group_member or other moderation tools.

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?

It says to use the pending member's id from get_my_group and that mcp:manage is required, which gives useful sourcing and permission context. However, it does not state when to use this tool versus alternatives or any conditions where it should not be used.

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