Skip to main content
Glama
io.github.ryanmat/logicmonitor

io.github.ryanmat/logicmonitor

by ryanmat

get_recipient_groups

Read-onlyIdempotent

List LogicMonitor recipient groups with pagination and name filtering; optionally include each group's full recipient list to review notification targets.

Instructions

List recipient groups

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_recipient_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results
detailNoWhen true, fetch each group's full recipient list via an extra GET per group. Off by default to avoid N+1 API calls.
offsetNoPagination offset
name_filterNoFilter by group name (supports wildcards)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.0.1
    • addedInput schema / properties / offset
      Added value: +{
      +  "default": 0,
      +  "description": "Pagination offset",
      +  "type": "integer"
      +}
  2. First observedv4.2.0

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds nothing beyond that — notably it does not mention the costly N+1 behavior of the detail flag, which lives only in the schema.

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?

The single phrase contains no wasted words and is trivially front-loaded, but its brevity reflects under-specification rather than disciplined concision. There is nothing structured or actionable in it.

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 four optional parameters, no output schema, and a dozen similarly named sibling group-list tools, the description should at minimum distinguish listing from single-fetch and hint at pagination or filtering. It does none of this, leaving the schema to do all the work.

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%, including a clear explanation of the detail flag's extra GET-per-group cost, so the schema carries parameter meaning. The description contributes no parameter context at all, which is the baseline case when coverage is complete.

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

Purpose2/5

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

"List recipient groups" restates the tool name (get_recipient_groups) with no additional specificity. It gives no hint of what distinguishes it from the sibling get_recipient_group, so an agent must open the schema to tell list-from-get apart.

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 versus get_recipient_group or the many other get_*_groups siblings. No prerequisites, no scope conditions, and no exclusions are stated.

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