Skip to main content
Glama

group_removeMember

Remove a user from an Operaton group so they stop receiving task assignments for that group's candidate tasks.

Instructions

Remove a user from an Operaton group. The user will no longer receive task assignments for this group's candidate tasks.

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": {
      "id": "<id>",
      "userId": "<userId>"
    },
    "name": "group_removeMember"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
userIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.3.0
    • addedInput schema / properties / id
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / userId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "id",
      +  "userId"
      +]
  2. First observedv1.1.0

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does add real behavioral value by stating the consequence — the user stops receiving task assignments for the group's candidate tasks — which clarifies the effect of a mutation rather than just naming it. However, it omits required permissions, error behavior when the user is not a member, and whether other assignments are affected, leaving meaningful gaps for an unannotated write operation.

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 short sentences with no filler: the action is front-loaded and the consequence follows. Every sentence earns its place.

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 simple two-parameter mutation with no output schema, the description covers the action and its main side effect. It is still incomplete on prerequisites, failure modes, and parameter meanings, which matter for a write operation with zero annotation coverage.

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 for both parameters. It only indirectly implies that 'id' refers to the group (via 'from an Operaton group') and says nothing about 'userId' or its expected format, so the schema's two bare string fields remain largely unexplained.

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 and resource: 'Remove a user from an Operaton group.' The verb 'remove' naturally contrasts with the sibling 'group_addMember' without needing to name it, so an agent can distinguish membership removal from membership addition and from group_create/group_delete.

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 explicit when-to-use guidance, no statement of prerequisites (must the user already be a member? must the group exist?), and no mention of what happens on failure or whether the operation is idempotent. The agent must infer the calling context entirely.

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