Skip to main content
Glama
monitoringartist

LogicMonitor MCP Server

list_resource_group_properties

Read-only

View all custom properties applied to a resource group in LogicMonitor, including inherited values for device configuration and authentication.

Instructions

List all custom properties for a specific resource/device group in LogicMonitor (LM) monitoring. Properties set at group level are inherited by all resource/device in the group.

Returns: Array of properties with: name, value, type (custom vs system), and inheritance source.

When to use:

  • Review properties before bulk updates

  • Audit credentials/settings applied to resource/device group

  • Verify property inheritance from parent groups

  • Check which properties resource/device will inherit when added to group

  • Document group configuration

What are group properties: Key-value pairs set at group level that ALL resource/device in the group inherit. Common uses: credentials (SSH/SNMP), environment tags, owner/team info, monitoring settings.

Property inheritance:

  • Properties set on group apply to ALL resource/device in group

  • Child groups inherit from parent groups

  • Device-level properties override group properties

  • Used by datasource "appliesTo" logic and authentication

Common group properties:

  • Credentials: ssh.user, ssh.pass, snmp.community, wmi.user, wmi.pass

  • Tags: env (production/staging), location (datacenter), owner (team name)

  • Business metadata: cost.center, sla.tier, compliance.level

  • Monitoring config: polling.interval, alert.threshold.multiplier

Use cases:

  • Audit credentials: Check which credentials are configured for group

  • Before bulk update: See current values before changing

  • Troubleshoot authentication: Verify credentials applied to resource/device

  • Document configuration: Export group settings

Workflow: Use "list_resource_groups" to find groupId, then use this tool to see properties, then "update_device_group_property" to modify.

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: "update_device_group_property" (modify property), "get_resource_group" (group details), "list_device_properties" (device-level properties).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupIdYesThe resource/device group ID
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.
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the tool is read-only. The description adds details about return format (array of properties with fields) and an important behavioral note about negative 'total' values indicating incomplete results and pagination behavior. This goes beyond 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 relatively long but well-structured with sections (When to use, Property inheritance, Common properties, Use cases, Workflow, Important). It is front-loaded with the core purpose. Each section adds value, though some redundancy exists (e.g., use cases overlapping with when-to-use).

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 explains the return format and lists possible fields (name, value, type, inheritance source). It covers domain context like property inheritance, common examples, and workflow. For a list tool, this is highly complete and leaves minimal ambiguity.

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%, so baseline is 3. The description does not add significant parameter-specific semantics beyond the schema. It provides context about property types and inheritance but doesn't elaborate on individual parameters. The schema descriptions are sufficient.

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 it lists custom properties for a resource/device group, and distinguishes from related tools like list_resource_properties (device-level) and update_device_group_property. The specific verb 'list' and resource 'group properties' are unambiguous.

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

Usage Guidelines4/5

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

The description provides a dedicated 'When to use' section with specific scenarios (bulk updates, audit, verify inheritance) and a workflow linking to sibling tools. It lacks explicit when-not-to-use but offers clear guidance on appropriate use cases.

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