Skip to main content
Glama

Get Group

get_group
Read-only

Retrieve detailed Microsoft 365 group information by group ID to support lookup, administration, and group management tasks.

Instructions

Get detailed group information

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

Input Schema

NameRequiredDescriptionDefault
group_idYesGroup ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

Annotations declare readOnlyHint=true, so the safety profile is covered. Beyond that, the description adds only the word "detailed" without explaining what fields are returned, whether lookups fail for inaccessible groups, or how the group is identified. For a tool with no output schema, that leaves a real informational gap.

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, front-loaded sentence with no filler. However, its brevity comes from under-specification rather than disciplined compression — there is no substance left after the name is restated.

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?

With no output schema, the description should say what "detailed" covers (members, owners, visibility, mail settings). It also says nothing about failure modes for a lookup that commonly fails on permissions. As written, an agent knows only the verb and resource.

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?

There is a single required parameter, group_id, and schema coverage is 100%, so the schema fully documents it. The description adds nothing (such as whether the ID is an object ID or email), which meets the baseline of 3 for fully covered schemas.

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?

"Get detailed group information" states a verb (get) and resource (group), so the basic operation is clear. But it essentially restates the title and name, and it gives no signal to distinguish it from siblings such as list_group_members or get_contact beyond the word "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, no prerequisites, and no note about whether the caller must be a member of the group. The agent must infer everything about selection context.

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

Deploy Server

Other Tools