Skip to main content
Glama
monitoringartist

LogicMonitor MCP Server

list_resource_groups

Read-only

List all resource groups in LogicMonitor to browse organizational folders, find group IDs, and understand hierarchy for monitoring management.

Instructions

List all resource/device groups (folders) in LogicMonitor (LM) monitoring.

Returns: Array of groups with: id, name, parentId, full path, description, number of resources/devices, number of subgroups, custom properties.

What are groups: Organizational folders for resources/devices, like directories in a file system. Used to organize by location, environment, customer, or any logical structure.

When to use:

  • Browse resource/device organization

  • Find group IDs for resource/device creation/assignment

  • Understand resource/device hierarchy

  • Get group IDs for group-level operations (properties, SDT)

Common use cases:

  • Geographic: "US-West", "EU-Central", "APAC"

  • Environment: "Production", "Staging", "Development"

  • Customer: "Customer-A", "Customer-B" (for MSPs)

  • Function: "Web Servers", "Database Servers", "Network resources/Devices"

Common filter patterns:

  • By name: filter:"name~*Production*"

  • Root groups: filter:"parentId:1"

  • Non-empty: filter:"numOfDirectDevices>0"

Groups inherit properties: Custom properties set on group are inherited by all resource/device in that group (useful for credentials, location tags).

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_resource_group" (details), "create_resource_group" (create new), "list_resource_group_properties" (group properties).

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?

Adds behavioral context beyond readOnlyHint annotation: explains negative total meaning, pagination, property inheritance, and filter syntax.

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?

Well-structured with sections, front-loaded purpose, but lengthy; every sentence is useful but could be slightly more concise.

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?

Completes the picture with output structure, use cases, filter patterns, property inheritance, and related tools, compensating for no output schema.

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%, description adds value with filter pattern examples and pagination guidance, but does not deeply elaborate on each parameter.

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?

Clearly states the tool lists all resource/device groups, defines what groups are, and distinguishes from siblings like get_resource_group and list_resource_group_properties.

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 when to use with bullet points, provides common use cases and filter patterns, and mentions related tools for 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