Skip to main content
Glama
EntraID MCP Server

EntraID MCP Server

by baoduy

Remove Group Member

remove_group_member
Destructive

Remove a member from a group.

Instructions

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>",
      "member_id": "<member_id>"
    },
    "name": "remove_group_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
group_idYesID of the group
member_idYesID of the member to remove

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is covered structurally. The description adds nothing beyond that — no note on irreversibility, effect on the member's other memberships, permission requirements, or error behavior if the member is not in the group. It is consistent with annotations, just not additive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence with zero waste and the action front-loaded, but the brevity comes at the cost of substance rather than from efficient editing of rich content.

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?

This is a destructive mutation with an output schema available, so return values need not be explained. However, the description says nothing about side effects, preconditions, or failure modes, leaving a destructive operation under-described relative to its risk.

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 description coverage is 100% with only two required string parameters, so the schema fully documents group_id and member_id. The description adds no format, sourcing, or lookup guidance beyond the schema, which is the expected baseline of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a verb and resource (remove a member from a group), which is understandable, but it nearly restates the tool name 'remove_group_member' and offers no differentiation from close siblings such as add_group_member, remove_group_owner, or delete_group.

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 tool versus alternatives, nor any preconditions (e.g., member must currently belong to the group). The agent must infer everything from the name and schema.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.