Skip to main content
Glama
outlook-mcp

outlook-mcp

by Plong-Wasin

list_distribution_groups

Retrieve mail-enabled distribution groups in your organization to find shared email addresses and manage results with pagination or display-name search.

Instructions

List mail-enabled Distribution Groups in the organisation (classic distribution lists). Each group has a single email address that delivers to all its members.

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": "list_distribution_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNoMaximum number of groups to return (default: 50, max: 999)
skipNoNumber of groups to skip (for pagination)
searchNoSearch string to filter groups by display name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It explains what a distribution group is, but does not disclose read-only safety, required permissions, pagination behavior, or whether all groups are returned by default.

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?

Two short sentences with no filler. The resource is stated first and the definition of a classic distribution list is included because it aids interpretation.

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 list tool with three fully documented optional parameters and no output schema, the description provides enough context to understand what is being listed. The main gap is that it does not mention pagination or alternative list tools, but the schema covers the parameters.

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 100%, so the input schema already documents top, skip, and search fully. The description adds no parameter-specific meaning beyond the schema, which makes 3 the appropriate baseline.

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

Purpose4/5

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

The description states a specific verb and resource: 'List mail-enabled Distribution Groups in the organisation,' and clarifies that these are 'classic distribution lists' with a single email address. This is clear enough to distinguish it conceptually from sibling tools like list_users or list_group_members, though it does not explicitly name an alternative.

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 explicit guidance on when to use this tool versus related tools such as list_group_members, list_users, or list_contacts. The purpose implies usage, but the description provides no exclusions, prerequisites, or alternative-selection criteria.

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