Skip to main content
Glama
monitoringartist

LogicMonitor MCP Server

get_collector

Read-only

Get detailed health and status information for a specific LogicMonitor collector by its ID, such as alive/dead status, number of monitored hosts, free disk space, and build version.

Instructions

Get detailed information about a specific collector by its ID in LogicMonitor (LM) monitoring.

Returns: Complete collector details: description (name), hostname, platform, status, build version, number of resource/device monitored, free disk space, CPU/memory usage, last heartbeat, configuration.

When to use:

  • Check collector health before assigning resources/devices

  • Verify collector capacity

  • Troubleshoot connectivity issues

  • Check version for updates

  • Monitor collector performance

Health indicators to check:

  • status: "alive" (healthy) vs "dead" (offline/problem)

  • numberOfHosts: How many resource/device this collector monitors (capacity planning)

  • freeDiskSpace: Disk space available (needs GB for data buffering)

  • build: Version number (compare with "list_collector_versions" for updates)

  • lastHeartbeatTime: Recent = healthy, old = potential issue

Workflow: Use "list_collectors" to find collectorId, then use this tool for detailed health check.

Related tools: "list_collectors" (find collector), "list_collector_versions" (check updates), "list_resources" (see assigned resources/devices).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collectorIdYesThe ID of the collector to retrieve
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. Description adds value by listing specific health indicators (status, numberOfHosts, freeDiskSpace) and their meanings, going beyond the bare annotation.

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 (Returns, When to use, Health Indicators, Workflow, Related tools). Though lengthy, the structure aids comprehension and all content adds value.

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?

No output schema; description fully details return fields (description, hostname, platform, etc.) and health interpretations. With only 2 parameters, this is thorough and complete for agent invocation.

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 coverage is 100%, so baseline is 3. Description adds examples for 'fields' parameter and explains the curated set vs '*', providing extra clarity.

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 states 'Get detailed information about a specific collector by its ID' with clear verb+resource. It distinguishes from siblings like 'get_collector_group' and 'list_collectors' by focusing on a single collector's details.

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 lists when to use (check health, capacity, troubleshoot) and provides workflow ('list_collectors' to find ID, then this tool). Also mentions related tools, giving clear context for decision-making.

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