Skip to main content
Glama
EntraID MCP Server

EntraID MCP Server

by baoduy

Get All Groups

get_all_groups
Read-only

Get all groups (up to the specified limit, with paging).

Instructions

Get all groups (up to the specified limit, with paging).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_all_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds genuinely new context by disclosing paging and a limit-bounded result set, which the annotation does not express, but says nothing about pagination mechanics or rate limits.

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 no filler; the paging qualifier is placed inline where it matters. It is efficient, though its brevity comes at the cost of substance.

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?

An output schema exists, so return values need not be explained, and the tool has one optional parameter. Still, for a bulk-listing endpoint the description leaves paging semantics and sibling disambiguation unaddressed, which an agent may need to call it correctly.

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% and the single 'limit' parameter has no documented semantics. The description mentions 'up to the specified limit, with paging' but does not clarify whether limit caps the total result count or the page size, nor what the default behavior is.

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?

States a concrete verb and resource ('Get all groups'), so the basic operation is clear. But it does not distinguish itself from siblings like search_groups_by_name or get_group_by_id, leaving the agent to infer why an unfiltered listing exists alongside a name search.

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 bulk listing versus search_groups_by_name or get_group_by_id, and no mention of prerequisites or expected scale. The agent gets no routing signal from the description.

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