Skip to main content
Glama
monitoringartist

LogicMonitor MCP Server

list_resource_instances

Read-only

Retrieve all monitored instances (e.g., disks, network interfaces) for a specific device and datasource, providing IDs for metric retrieval.

Instructions

List instances of a datasource on a specific resource/device in LogicMonitor (LM) monitoring.

Returns: Array of instances with: id, name, displayName, description, status, alert status, last collection time.

What are instances: Individual components monitored by a datasource. Examples: individual disks (C:, D:, E:), network interfaces (eth0, eth1), database tables, processes.

When to use:

  • List all disks on a server before getting disk metrics

  • Find specific network interface for bandwidth data

  • Discover what instances are being monitored

  • Get instance IDs for metric retrieval

Example workflow: Device "web-server-01" has datasource "WinVolumeUsage-" → instances: C:, D:, E: (each disk is an instance) Device "router-01" has datasource "SNMP_Network_Interfaces" → instances: GigabitEthernet0/1, GigabitEthernet0/2 (each interface is an instance)

Complete workflow to get metrics:

  • Use "list_resource_datasources" to get deviceDataSourceId

  • Use this tool to list instances and get instanceId

  • Use "get_resource_instance_data" with instanceId to get actual metrics

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: "list_resource_datasources" (first step), "get_resource_instance_data" (get metrics).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deviceIdYesThe resource/device ID
deviceDataSourceIdYesThe resource/device datasource 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.
Behavior5/5

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

Annotations indicate readOnlyHint=true, and description aligns perfectly by describing a read operation. Adds behavioral context beyond annotations: return structure (array with fields), pagination behavior, and significance of negative total. 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?

Description is well-structured with headers and bullet points, front-loading purpose. While somewhat lengthy, every section serves a purpose (examples, workflow, important notes). Minor verbosity is justified for a tool involved in multi-step processes.

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, description compensates by listing returned fields. Explains concept of instances, provides examples, details pagination behavior, and outlines complete workflow. Covers all essential context for an agent to use the tool correctly.

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?

Input schema has 100% description coverage, so baseline is 3. Description adds value by explaining workflow context (deviceDataSourceId from list_resource_datasources), filter syntax examples, and autoPaginate behavior, which goes beyond schema descriptions.

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?

Description clearly states the tool lists instances of a datasource on a specific resource/device, with a specific verb and resource. It distinguishes from sibling tools like list_resource_datasources by focusing on instances rather than datasources.

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 provides 'When to use' bullets and a 'Complete workflow to get metrics' that positions this tool in a sequence with siblings. Also warns about negative total indicating incomplete results and suggests pagination, giving clear guidance on when to use pagination.

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