Skip to main content
Glama
monitoringartist

LogicMonitor MCP Server

list_opsnotes

Read-only

List all operational notes (OpsNotes) to correlate metric changes with deployments, incidents, and maintenance. Timestamped annotations document operational events and appear on graphs.

Instructions

List all operational notes (OpsNotes) in LogicMonitor (LM) monitoring.

Returns: Array of OpsNotes with: id, note text, timestamp (epoch), who created it, tags, scope (applies to which resources/devices/groups), related SDTs.

What are OpsNotes: Timestamped operational annotations displayed on graphs and dashboards. Document changes, deployments, maintenance, incidents - anything that might affect metrics. Appear as vertical lines on metric graphs at the time they occurred.

When to use:

  • Correlate metric changes with operational events

  • Document deployments/changes

  • Create timeline of incidents and responses

  • Track maintenance activities

  • Generate operational reports

Use cases and examples:

Deployments:

  • "Deployed v2.5.0 to production" (explains CPU spike at deploy time)

  • "Database schema migration" (explains slow queries during migration)

Incidents:

  • "Customer reported slow load times - investigating"

  • "Found memory leak, restarting services"

  • "Incident resolved - bad cache configuration"

Maintenance:

  • "Scaled from 10 to 15 instances"

  • "Updated SSL certificates"

  • "Cleared old logs, freed 500GB disk"

Benefits:

  • Troubleshooting: "Latency increased at 2pm" → Check OpsNotes: "Deploy happened at 2pm"

  • Correlation: Understand cause of metric anomalies

  • Documentation: Automatic operational timeline

  • Communication: Share what happened with team

Common filter patterns:

  • By time: filter:"happenedOn>1730851200" (recent notes)

  • By tags: filter:"tags~deployment"

  • By device: filter:"monitorObjectName~prod-web"

Displayed on: Graphs, dashboards, resource/device pages - visible wherever metrics are shown.

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_opsnote" (details), "create_opsnote" (add new), "create_device_sdt" (maintenance windows).

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.
Behavior5/5

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

Beyond the readOnlyHint annotation, the description details return format (Array of OpsNotes with specific fields), behavior with negative total indicating incomplete results, and pagination mechanics via autoPaginate. No contradictions 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.

Conciseness4/5

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

Description is verbose but well-structured with clear headers (When to use, Use cases, Benefits, filter patterns, etc.). Front-loads purpose but includes extensive examples and benefits that could be condensed. Loses one point for length.

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, full schema coverage, and no output schema, the description is complete: explains return structure, common use cases, pagination nuances, and related tools. No gaps identified.

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?

Input schema provides 100% coverage with full parameter descriptions. The description adds no new parameter semantics beyond what the schema already provides (e.g., filter patterns and pagination are already in schema). Baseline 3 applies.

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 operational notes (OpsNotes) in LogicMonitor, with specific verb and resource. It distinguishes from siblings by mentioning related tools like get_opsnote, create_opsnote, and create_device_sdt.

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?

Provides explicit 'When to use' section listing scenarios, covers when not to use (alternative tools), and includes filter patterns and pagination advice. The description clearly guides the AI agent on context and 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