Skip to main content
Glama
monitoringartist

LogicMonitor MCP Server

by monitoringartist
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

list_collector_versions

Read-only

Retrieve all available LogicMonitor collector versions with version numbers, release dates, stability levels, and changelogs to check for updates and plan upgrades.

Instructions

List available collector versions in LogicMonitor (LM) monitoring.

Returns: Array of collector versions with: version number, release date, stability level (GA/EA/RC), changelog summary, download size, platform support (Windows/Linux), mandatory/recommended flag.

What are collector versions: Software releases for LogicMonitor collector agents. Collectors are installed on your infrastructure to gather monitoring data. Staying current ensures latest features, bug fixes, and security patches.

When to use:

  • Check for collector updates

  • Review changelog before upgrading

  • Find specific version for rollback

  • Verify platform compatibility

  • Plan maintenance windows for collector upgrades

Version types:

  • GA (Generally Available): Production-ready, stable, recommended

  • EA (Early Adopter): Beta, new features, use in non-production first

  • RC (Release Candidate): Pre-GA testing version

  • Mandatory: Critical security/bug fixes, upgrade required

Collector update workflow: 1. Use this tool to check available versions 2. Review changelog for breaking changes 3. Test new version on non-production collector first 4. Use "get_collector" to check current version on your collectors 5. Update collectors via LogicMonitor UI or API 6. Monitor collector health after upgrade

Version numbering: Format is typically X.Y.Z (e.g., 34.100.0) where:

  • X = Major release (significant changes)

  • Y = Minor release (features, improvements)

  • Z = Patch release (bug fixes)

Best practices:

  • Keep collectors within 2-3 versions of latest GA release

  • Subscribe to release notifications for critical updates

  • Test EA versions in lab before production

  • Upgrade during maintenance windows (may briefly interrupt monitoring)

  • Stagger upgrades (don't upgrade all collectors simultaneously)

Common scenarios:

  • "Check if newer version available" → Compare latest version to your collectors

  • "Plan upgrade" → Review changelog, schedule maintenance

  • "Rollback needed" → Find previous stable version

  • "Platform migration" → Verify version supports new OS

Related tools: "get_collector" (check current version on collector), "list_collectors" (find collectors to upgrade).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sizeNoNumber of results per page (default: 50, max: 1000).
offsetNoStarting offset for pagination (default: 0).
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.

Tool Definition Quality

A4.5/5.0
Behavior5/5

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

Annotations already indicate readOnlyHint, but the description provides extensive behavioral context: the return format (array with fields), version types (GA, EA, RC, mandatory), and workflow. There is no contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with headings and bullet points, but it is verbose with sections on version numbering, best practices, and detailed workflow. While informative, it could be more concise for a tool definition.

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?

With no output schema, the description fully explains return values. It covers version types, use cases, best practices, and links to related tools. The 3 optional parameters are well-documented in the schema, so the description is complete for the tool's complexity.

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%, so baseline 3. The description does not elaborate on parameters beyond what the schema provides. It focuses on output and usage, not parameter details.

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 first sentence clearly states the tool lists available collector versions in LogicMonitor. It specifies the verb, resource, and context. The description further distinguishes from siblings by mentioning related tools like 'get_collector' and 'list_collectors' for specific tasks.

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 'When to use' section lists five explicit scenarios (check updates, review changelog, find rollback, verify platform, plan upgrades). It also provides 'Common scenarios' and mentions related tools, giving clear guidance on when to use this tool versus alternatives.

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