Skip to main content
Glama
monitoringartist

LogicMonitor MCP Server

get_recipient_group

Read-only

Get detailed information about a recipient group by ID, including member contacts and escalation chain usage. Useful for auditing team notification lists and understanding impact before modifying the group.

Instructions

Get detailed information about a specific recipient group by ID in LogicMonitor (LM) monitoring.

Returns: Complete recipient group details: name, description, list of all members (recipients), member contact info, escalation chains using this group.

When to use:

  • Review group membership before modifications

  • Verify who gets notified through this group

  • Check which escalation chains use this group

  • Audit team notification lists

Key information returned:

  • Members: All recipients in group (names, emails, phones)

  • Usage: Which escalation chains reference this group

  • Description: Purpose/team name

Before modifying group: Review escalation chain usage to understand impact of changes. Removing member from group affects all chains using that group.

Workflow: Use "list_recipient_groups" to find groupId, then use this tool to review membership before updating.

Related tools: "list_recipient_groups" (find groups), "update_recipient_group" (modify), "list_escalation_chains" (see where used).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupIdYesThe ID of the recipient group to retrieve
fieldsNoComma-separated list of fields to include in response. Examples: "id,displayName,hostStatus" or use "*" for all fields. Omit this parameter to receive a curated set of commonly used fields.
Behavior5/5

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

Annotations already indicate readOnlyHint=true, and the description adds valuable context: what information is returned (members' contact info, escalation chain usage), and the caution that removing a member affects all chains using the group. No contradictions.

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?

The description is well-structured with sections (Returns, When to use, Key information, Warning, Workflow, Related tools). It is comprehensive but slightly lengthy; however, every section serves a purpose and adds clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, the description exhaustively explains return values (members, usage, description) and provides workflow guidance and warnings. For a tool with two parameters, this is thorough and leaves no ambiguity for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Both parameters are described in the schema (100% coverage), and the description adds meaning: groupId is obtained from list, and fields can be a comma-separated list or '*' with an explanation of omitting it. It reinforces the purpose but doesn't introduce new meanings beyond 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 clearly states the tool retrieves detailed info about a specific recipient group by ID, and lists what details are returned (members, usage, description). It distinguishes from siblings like 'list_recipient_groups' and 'update_recipient_group' by specifying its role in the workflow.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly lists four usage scenarios (review membership before modifications, verify notifications, check escalation chain usage, audit notification lists) and suggests a workflow: use 'list_recipient_groups' to find groupId, then this tool before updating. Also mentions related tools and warns about impact of changes.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/monitoringartist/logicmonitor-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server