Skip to main content
Glama
monitoringartist

LogicMonitor MCP Server

get_resource_group

Read-only

Retrieve a LogicMonitor resource group's full details, including hierarchy, inherited custom properties, device counts, and alert status.

Instructions

Get detailed information about a specific resource/device group by its ID in LogicMonitor (LM) monitoring.

Returns: Complete group details: name, full path, parentId, description, custom properties, number of resource/device (direct and total), number of subgroups, alert status, SDT status.

When to use:

  • Get group path for documentation

  • Review inherited properties

  • Check group membership counts

  • Verify group hierarchy

  • Get group details before creating resource/device in it

Key information:

  • fullPath: Complete hierarchy (e.g., "/Production/Web Servers/US-East")

  • customProperties: Properties inherited by all resource/device in group

  • numOfDirectDevices: resources/Devices directly in this group

  • numOfHosts: Total resource/device including subgroups

  • alertStatus: Rollup alert status for entire group

Custom properties inheritance: Properties set on group are inherited by ALL resource/device in group. Common uses:

  • Credentials: {name: "ssh.user", value: "monitoring"}

  • Environment tags: {name: "env", value: "production"}

  • Owner: {name: "team", value: "platform-engineering"}

Workflow: Use "list_resource_groups" to find groupId, then use this tool for complete details including inherited properties.

Related tools: "list_resource_groups" (find groups), "create_resource_group" (create new), "list_resources" (devices in group).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupIdYesThe ID of the resource/device 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 include readOnlyHint=true, but the description adds valuable behavioral context: it explains the returned structure (fullPath, customProperties, etc.) and details about custom properties inheritance. No contradiction with annotations.

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 lengthy but well-organized into sections (returns, when to use, key information, etc.). It is front-loaded with the core purpose and each section adds distinct value. Not overly verbose for a complex tool.

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 no output schema, the description thoroughly explains the return fields (fullPath, customProperties, numOfDirectDevices, etc.) and inheritance behavior. It is complete for a get tool with two parameters.

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% (both parameters documented). The description does not add new parameter details but explains the significance of returned fields, which helps interpret the output. The value-add justifies a score above baseline 3.

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 obtains detailed information about a resource/device group by ID, using specific verb and resource. It distinguishes from siblings like list_resource_groups which lists groups, and get_resource which gets a device.

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 description provides explicit 'When to use' scenarios, a workflow referencing list_resource_groups, and related tools. It gives clear context on when to use this tool, such as checking group membership or reviewing inherited properties.

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