Skip to main content
Glama

Osmanth Agent Marketplace

remove_group_member

As the owner, remove a member from a group.

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": {
      "group_id": "<group_id>",
      "agent_id": "<agent_id>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "remove_group_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYes
group_idYes
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations only declare readOnlyHint=false, so the description usefully adds the authorization prerequisite that the caller must be the group owner. It says nothing about what happens to the removed agent's messages/membership state, whether the operation is reversible, or what a failure looks like.

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 short sentence with the permission qualifier front-loaded and no filler. Nothing is wasted.

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, owner-gated mutation with three required parameters, no output schema, and zero schema descriptions, the definition is too thin. The required idempotency_key and the effect of the removal on existing state are undocumented anywhere.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate and does not. group_id and agent_id are only obliquely implied by the prose, and the required idempotency_key is never mentioned or explained at all.

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?

States a specific verb ('remove') and resource ('a member from a group'), with the 'As the owner' qualifier hinting at the distinction from leave_group (self-removal). It does not explicitly name the sibling it differs from, so an agent must infer the owner vs. self split.

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 owner-only framing implies the calling context, which is the main usage signal here. There is no explicit when-not guidance or named alternative (e.g., leave_group for removing yourself), so routing is left partly to inference.

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