Skip to main content
Glama
monitoringartist

LogicMonitor MCP Server

list_resources

Read-only

Retrieve inventory of all monitored resources/devices. Filter by name, status, or custom properties using simple search or advanced LM filter syntax.

Instructions

List all monitored resources/devices in LogicMonitor (LM) monitoring.

Returns: Array of resource/device with: id, displayName, name (IP/hostname), hostStatus (dead/alive/unknown), preferredCollectorId, deviceType, custom properties, group memberships.

When to use:

  • Get inventory of all monitored resources/devices

  • Find specific resource/device by name/IP/property

  • Check resource/device health status

  • Get resource/device IDs for other operations

Two search modes:

  • Simple search: Use query parameter with free text (e.g., query:"production", query:"web-server") - automatically searches displayName, description, and name fields

  • Advanced filtering: Use filter parameter with LM filter syntax (e.g., filter:"hostStatus:alive,displayName~*web*") for precise control

Common filter patterns:

  • By name: filter:"displayName~*prod*" (wildcard search)

  • By status: filter:"hostStatus:alive" or filter:"hostStatus:dead"

  • By type: filter:"systemProperties.name:system.devicetype,value:server"

  • By custom property: filter:"customProperties.name:company.team,customProperties.value:teamA"

  • By collector: filter:"preferredCollectorId:123"

  • Multiple conditions: filter:"hostStatus:alive,displayName~*web*" (comma = AND)

Query vs Filter:

  • query: Simplified search across displayName, description, name (OR logic). Use for quick lookups: query:"prod-web-01"

  • filter: Precise LM filter syntax with any field. Use for complex conditions: filter:"hostStatus:alive,displayName~*prod*"

  • If both provided, query is converted to filter and combined with provided filter using AND logic

Important: A negative "total" value in the response indicates incomplete results. Use pagination (size/offset parameters) or set autoPaginate: true to retrieve all items.

Performance tips: Use autoPaginate:false for large environments (>1000 resources/devices) and paginate manually to avoid timeouts.

Related tools: "get_resource" (details), "generate_resource_link" (get UI link).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoSimple search query. Free text (e.g., "production", "web-server", "192.168.1.100") automatically searches across displayName, description, and name fields. Can also use filter syntax (e.g., "hostStatus:alive") which gets formatted automatically.
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 already indicate readOnlyHint=true, and the description confirms read-only behavior. It additionally discloses potential incomplete results (negative total), autoPaginate default behavior, and performance considerations. 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?

Well-structured with sections, bullet points, and examples. Every section adds value, but some redundancy exists (e.g., query vs filter explained twice). Not perfectly concise but still clear and organized.

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 the tool's complexity (6 parameters, no output schema), the description covers usage contexts, both search modes with examples, filter syntax, pagination handling, and performance guidance. It also links to related tools. Highly complete.

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% coverage, but the description adds significant value by explaining search modes (query vs filter), common filter patterns, and pagination behavior. It goes beyond the schema's minimal descriptions, warranting a score above baseline.

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 all monitored resources/devices in LogicMonitor. It distinguishes from sibling tools like get_resource (details) and generate_resource_link (UI link), and uses specific verbs and resource naming.

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 states when to use (inventory, find by name/IP, check health, get IDs), compares query vs filter search modes, provides common filter patterns, and mentions pagination and performance tips. Also references related tools.

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