Skip to main content
Glama
monitoringartist

LogicMonitor MCP Server

list_service_groups

Read-only

Retrieve all service groups (folders) to browse the service hierarchy and find group IDs for monitoring operations.

Instructions

List all service groups (folders) in LogicMonitor (LM) monitoring.

Returns: Array of service groups with: id, name, parentId, full path, description, number of services, number of subgroups.

What are service groups: Organizational folders for business services, similar to resource/device groups for resources/devices. Used to categorize services by business unit, region, customer, or application stack.

When to use:

  • Browse service organization before creating services

  • Find group IDs for service operations

  • Understand service hierarchy

  • Navigate to specific service folders

Common organization patterns:

  • By business unit: "E-Commerce", "Marketing Platform", "Internal IT"

  • By customer: "Customer A Services", "Customer B Services" (MSP environments)

  • By region: "APAC Services", "EMEA Services", "Americas Services"

  • By tier: "Tier 1 Critical", "Tier 2 Standard", "Tier 3 Best Effort"

Use cases:

  • Organize services for different stakeholders

  • Group services by SLA tiers

  • Separate internal vs customer-facing services

  • Structure multi-tenant service monitoring

Workflow: Use this tool to browse hierarchy, then "list_services" filtered by groupId to see services in specific folder.

Important: A negative "total" value in the response indicates incomplete results. Use pagination (size/offset parameters) or set autoPaginate: true to retrieve all items.

Related tools: "get_service_group" (details), "list_services" (services in group), "create_service_group" (create folder).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sizeNoNumber of results per page (default: 50, max: 1000).
offsetNoStarting offset for pagination (default: 0). Use this to skip a specific number of results.
autoPaginateNoAutomatically fetch all pages (default: false). When true, fetches all results across multiple pages. When false, returns only the requested page. Use false for large result sets to avoid long response times.
filterNoFilter expression using LogicMonitor query syntax. Examples: name:*prod*, displayName~*server*, id>100, hostStatus:normal. Available operators: : (equals), ~ (includes), !: (not equals), !~ (not includes), >: (greater than or equals), <: (less than or equals), > (greater than), < (less than). Multiple conditions: Use comma (,) for AND, use || for OR. Do NOT use &&.
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 value by detailing return fields, the meaning of negative total, and pagination behavior. 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, but slightly lengthy. However, each section adds value, and the key purpose is front-loaded. Minor deduction for verbosity.

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?

Given 5 parameters and no output schema, the description covers return fields, use cases, organization patterns, workflow, and pagination details. It is comprehensive and leaves no critical gaps.

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?

Schema coverage is 100%, so the schema already describes all parameters. The description adds context like the meaning of negative total and the effect of autoPaginate, which is valuable 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 'List all service groups (folders) in LogicMonitor (LM) monitoring.' It specifies the verb (list) and resource (service groups), and distinguishes from sibling tools like get_service_group (details) and list_services (services in group).

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?

The 'When to use' section explicitly lists scenarios: browse before creating, find IDs, understand hierarchy, navigate. It also provides workflow guidance and mentions related tools, helping the agent choose this tool over alternatives.

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