Skip to main content
Glama
EntraID MCP Server

EntraID MCP Server

by baoduy

Search Groups By Name

search_groups_by_name
Read-only

Search for groups whose display name starts with the given text (case-insensitive, with paging).

Instructions

Search for groups whose display name starts with the given text (case-insensitive, with paging).

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": {
      "name": "<name>"
    },
    "name": "search_groups_by_name"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this as a read-only operation, and the description adds meaningful behavioral detail about case-insensitive prefix matching and paging. It stops short of describing return ordering or page-token behavior, but output schema coverage reduces the need for return details.

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 definition is a single front-loaded sentence with no wasted wording. It packs the operation, matching rule, and paging behavior into a compact statement.

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?

For a simple read-only search tool with an output schema and annotations, the description is nearly complete. The only remaining gap is that it does not explain how paging should be used or whether there is a next-page mechanism beyond limit.

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 0%, so the description must carry parameter meaning. It does well for name by specifying case-insensitive prefix matching, but limit is only indirectly covered by 'with paging' and its default of 50 is left solely to the schema.

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 states a specific verb (search) and resource (groups), and narrows the operation to display names beginning with a given text. It also specifies case-insensitive matching and paging, which clearly distinguishes it from broader group-listing tools like get_all_groups.

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 prefix-search condition implies when the tool is useful, but the description does not explicitly say when to use it instead of get_all_groups, get_group_by_id, or search_users. It gives enough context to infer basic use but no exclusion or alternative guidance.

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