Skip to main content
Glama
monitoringartist

LogicMonitor MCP Server

list_reports

Read-only

List all scheduled and on-demand reports in LogicMonitor to find existing reports, review schedules, and check recipients before creating duplicates.

Instructions

List all reports (scheduled and on-demand) in LogicMonitor (LM) monitoring.

Returns: Array of reports with: id, name, type (alert/availability/capacity/performance), description, schedule, recipients, format (PDF/HTML/CSV), last run time.

What are reports: Scheduled or on-demand documents summarizing monitoring data. Generate PDFs, HTML, or CSV files with metrics, alerts, availability statistics, capacity planning data. Automatically email to stakeholders.

When to use:

  • Find existing reports before creating duplicates

  • Review report schedules

  • Check who receives reports

  • Audit reporting configuration

Report types:

  • Alert Reports: Summary of alerts over time period (count by severity, MTTR, top alerting resources/devices)

  • Availability Reports: Uptime statistics, SLA compliance, outage summaries

  • Capacity Planning: Disk growth trends, CPU/memory usage over time, forecasting

  • Performance Reports: Metric trends, top consumers, performance baselines

  • Custom Reports: User-defined queries and visualizations

Common use cases:

  • Executive summaries: Monthly availability report to leadership

  • SLA reporting: Prove 99.9% uptime to customers

  • Capacity planning: Forecast when to add storage/servers

  • Compliance: Document monitoring coverage and alert response

  • Billing: Usage reports for chargebacks

Report schedules:

  • Daily: 8am delivery for NOC shift handoff

  • Weekly: Monday morning management briefing

  • Monthly: End-of-month SLA reports

  • Quarterly: Capacity planning reviews

  • On-demand: Generate for specific incidents/audits

Workflow: Use this tool to find reports, then "get_report" for details, or "generate_report" to run on-demand.

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_report" (details), "list_report_groups" (organization), "generate_report" (run now).

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?

Discloses return format (array of reports with fields), pagination behavior (negative total, autoPaginate), and provides rich additional context like report types, use cases, and schedules. Annotations declare readOnlyHint=true, and description aligns with that.

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 headers and bullet points, front-loading the main purpose. However, the extensive educational material on report types and use cases adds length. Could be trimmed without losing essential guidance, but still 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?

No output schema exists, so the description compensates by detailing return fields and behavior. Covers pagination, filter, fields, and related tools. Comprehensive enough for an agent to use correctly in various scenarios.

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 explaining pagination parameters in context (size, offset, autoPaginate) and filter syntax. It does not repeat parameter descriptions but provides useful usage tips beyond basics.

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 'List all reports (scheduled and on-demand) in LogicMonitor (LM) monitoring.' It uses a specific verb (list) and resource (reports), and distinguishes from sibling tools like 'get_report' (details) and 'list_report_groups' (organization).

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?

Explicit guidance on when to use (e.g., find existing reports before creating duplicates, review schedules) and when not (e.g., use 'get_report' for details). It also mentions related tools and workflows, including a 'Important' note about negative total indicating incomplete results.

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