Skip to main content
Glama
nelladath

EndpointRead-MCP

by nelladath

manage_entra_groups

Create, read, update, and delete Entra ID groups; manage group members and owners; search groups by name. Supports security, Microsoft 365, and dynamic groups.

Instructions

Manage Entra ID groups — full CRUD plus membership and ownership operations.

action values: list — List all groups get — Get group details (group_id) search — Search groups by displayName (search_term) create_security — Create a security group (body: {displayName, description}) create_m365 — Create a Microsoft 365 group (body) create_dynamic — Create a dynamic security group (body: includes membershipRule) update — Update group properties (group_id, body) delete — Delete a group (group_id, confirm=True) get_members — List group members (group_id) add_member — Add a member (group_id, member_id) remove_member — Remove a member (group_id, member_id) get_owners — List group owners (group_id) add_owner — Add an owner (group_id, member_id) bulk_add_members — Add multiple members (group_id, body: {member_ids:[...]})

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topNo
bodyNo
actionYes
confirmNo
group_idNo
member_idNo
search_termNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the confirm=True requirement for deletion, but does not mention permissions, reversibility, or error behaviors. Some behavioral context is added, but not comprehensive.

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 description is well-structured with a short summary sentence followed by a compact list of actions and parameter hints. Every line adds information, and there is no filler.

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?

Given the tool's complexity (14 actions, 7 parameters) and the presence of an output schema, the description covers all actions and their respective parameter needs. It lacks some operational context like prerequisites or error conditions, but is largely complete for selection and invocation.

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

Parameters5/5

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

Schema description coverage is 0%, and the description compensates thoroughly by mapping each action to its required parameters (e.g., create_security body includes displayName, description). This adds substantial meaning beyond the bare schema titles.

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

Purpose5/5

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

The description clearly states the tool manages Entra ID groups with full CRUD plus membership and ownership operations. It distinguishes from sibling tools by naming the specific resource (groups) and enumerating all actions.

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 description clearly implies usage for group management but provides no explicit when-to-use guidance or alternative tool comparisons. Since the resource is unambiguous, usage is implied rather than stated.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nelladath/EndpointRead-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server