Skip to main content
Glama
monitoringartist

LogicMonitor MCP Server

list_collectors

Read-only

List all monitoring collectors to check health, find available collectors, and monitor capacity before assigning resources.

Instructions

List all LogicMonitor (LM) monitoring collectors (monitoring agents).

Returns: Array of collectors with: id, description (collector name), hostname, platform (Windows/Linux), status (alive/dead), build version, number of monitored resources/devices, last heartbeat time.

When to use:

  • Check collector health status before adding resources/devices

  • Find available collectors for new resource/device assignments

  • Monitor collector capacity and load

  • Identify offline/dead collectors

What are collectors: Lightweight agents installed on-premise or in cloud that collect metrics from resources/devices. Each resource/device must be assigned to one collector.

Common filter patterns:

  • Alive collectors: filter:"status:alive"

  • By platform: filter:"platform:Linux" or filter:"platform:Windows"

  • By name: filter:"description~*prod*"

  • Low capacity: filter:"numberOfHosts<100"

Before creating resources/devices: Use this tool to find collectorId for the "preferredCollectorId" parameter in "create_resource".

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: "get_collector" (details), "list_collector_groups" (browse groups), "list_collector_versions" (check updates).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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 only have readOnlyHint:true, which is consistent. The description adds important behavioral details: a negative 'total' indicates incomplete results and recommends pagination or autoPaginate. It also clarifies the read-only nature but could mention any rate limits or auth requirements.

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, front-loaded with the main action, and each sentence adds value. It is slightly long but not wasteful; could be trimmed slightly for conciseness.

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 compensates by listing return fields and explaining collector concept. It covers filter syntax, pagination behavior, and prerequisite usage (finding collectorId). Completeness is excellent for this tool's complexity.

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%, so baseline is 3. The description adds value by providing common filter patterns and usage context (e.g., 'Before creating resources/devices'), which helps agents understand parameter use 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?

The description begins with a clear verb-resource combination: 'List all LogicMonitor (LM) monitoring collectors (monitoring agents).' It distinguishes this tool from siblings like get_collector and list_collector_groups through explicit related tools section and usage guidelines.

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 includes a dedicated 'When to use' section listing specific scenarios (check health, find available collectors, monitor capacity, identify offline) and explicitly recommends using this tool to find collectorId before creating resources, with a note on 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