Skip to main content
Glama
EntraID MCP Server

EntraID MCP Server

by baoduy

Add Group Owner

add_group_owner

Add an owner to a group.

Instructions

Add an owner to 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>",
      "owner_id": "<owner_id>"
    },
    "name": "add_group_owner"
  }
}

Input Schema

NameRequiredDescriptionDefault
group_idYesID of the group
owner_idYesID of the user to add as owner

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the safety profile is covered structurally. The description adds nothing further — no mention of idempotency, what happens if the user is already an owner, what permissions are required, or that the operation is additive and reversible via remove_group_owner.

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

Conciseness4/5

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

A single short sentence with zero waste, front-loaded with the verb. It is efficient, though efficiency here comes at the cost of information rather than through disciplined editing.

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?

An output schema exists, so return values needn't be explained, but for a mutation tool with no clarifying behavioral context the description should at least state permission requirements or the already-owner edge case. As written it is barely adequate for an agent to invoke it confidently.

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 coverage is 100% with both parameters fully documented, so the schema does the heavy lifting. The description adds no semantics beyond what the schema fields already say, which is the baseline-3 case for high coverage.

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

Purpose2/5

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

The description 'Add an owner to a group' essentially restates the title 'Add Group Owner'; the only content added is the clarification that owner_id is a user, which the schema already states. It doesn't differentiate from siblings like add_group_member or remove_group_owner beyond the obvious verb.

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?

No guidance on when to use this versus add_group_member, remove_group_owner, or update_group. No prerequisites (e.g., required Graph permissions, whether the user must already be a member) are mentioned.

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