Skip to main content
Glama
monitoringartist

LogicMonitor MCP Server

list_resource_properties

Read-only

Retrieve all system and custom properties for a device, including inherited values, to audit configuration and troubleshoot monitoring.

Instructions

List all custom properties (system and user-defined) for a specific resource/device in LogicMonitor (LM) monitoring.

Returns: Array of properties with: name, value, source (device-level vs inherited from group), type (system vs custom).

When to use:

  • Review resource/device configuration

  • Check credentials/authentication settings

  • See inherited vs device-specific properties

  • Troubleshoot datasource applies logic

  • Audit resource/device metadata

Property types:

System properties (auto-populated by LogicMonitor):

  • system.hostname: Device hostname

  • system.devicetype: Device category (server, network, cloud)

  • system.ips: IP addresses

  • system.categories: Auto-detected technologies (e.g., "AWS/EC2")

Custom properties (user-defined):

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

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

  • Integration IDs: servicenow.ci_id, jira.project

  • Business metadata: cost.center, sla.tier, backup.policy

Property inheritance: Properties can be set at: Device level (highest priority) → Group level → Parent group (inherited).

Datasource appliesTo logic uses properties: Many datasources check properties to decide if they should monitor device. Example: AWS_EC2 datasource checks if resource/device has "aws.resourcetype=ec2" property.

Workflow: Use "list_resources" to find deviceId, then use this tool to see all properties including inherited ones.

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_property" (modify), "get_resource" (see summary), "list_datasources" (see how properties affect monitoring).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deviceIdYesThe resource/device 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. The description adds significant behavioral context: return structure (name, value, source, type), inheritance hierarchy, the meaning of a negative 'total' value, and pagination details. This goes beyond the annotations to help the agent understand edge cases and output interpretation.

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 (Returns, When to use, Property types, Workflow, Important note) and front-loaded with the core purpose. It is relatively long but every section adds value, though some examples (e.g., detailed property lists) could be trimmed without losing essential guidance.

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?

For a tool with 6 parameters, no enums, no output schema, and 100% schema coverage, the description provides thorough context: usage scenarios, inheritance details, pagination pitfalls, property type examples, and a suggested workflow ('Use list_resources to find deviceId, then use this tool'). It covers what the agent needs to use the tool correctly.

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 coverage is 100% with good parameter descriptions. The description adds contextual usage notes (e.g., pagination behavior, filter examples) that aren't in the schema, but it doesn't significantly augment the semantics of individual parameters beyond what the schema already provides. Baseline 3 is appropriate.

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 starts with a specific verb ('List') and resource ('properties for a resource/device'), clearly distinguishing from sibling tools like list_resource_group_properties. It explicitly states the scope (system and user-defined) and the product (LogicMonitor).

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 includes a 'When to use' section listing five concrete scenarios (review configuration, check credentials, see inheritance, troubleshoot datasource, audit metadata) and mentions related tools (update_device_property, get_resource, list_datasources). It provides clear context for appropriate usage, though it could explicitly state when not to use.

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