Skip to main content
Glama
monitoringartist

LogicMonitor MCP Server

by monitoringartist
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

list_sdts

Read-only

List all scheduled maintenance windows (SDTs) to view active, upcoming, or expired downtimes and filter by status, device, or creator.

Instructions

List all Scheduled Down Times (SDTs) in LogicMonitor (LM) monitoring.

Returns: Array of SDTs with: id, type (DeviceSDT/DeviceGroupSDT/etc), device/group name, start/end times, duration, comment, creator, status (active/scheduled/expired).

What are SDTs: Maintenance windows that suppress alerting to prevent false alarms during planned work. No alerts are generated during SDT periods.

When to use:

  • View active maintenance windows

  • Check upcoming scheduled maintenance

  • Verify SDT was created correctly

  • Find SDTs to extend or cancel

  • Audit who scheduled downtime

Common filter patterns:

  • Active now: filter:"isEffective:true"

  • Future SDTs: filter:"startDateTime>{epoch}"

  • By device: filter:"deviceDisplayName~*prod-web*"

  • One-time vs recurring: filter:"type:oneTime" or filter:"type:monthly"

  • By creator: filter:"admin:john.doe"

SDT types explained:

  • DeviceSDT: All monitoring on specific resource/device

  • DeviceGroupSDT: All resource/device in group

  • DeviceDataSourceSDT: Specific datasource on resource/device

  • DeviceDataSourceInstanceSDT: Specific instance only (e.g., C: drive)

Best practice: Always add meaningful comment explaining maintenance reason for audit trail.

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: "create_resource_sdt" (schedule maintenance), "delete_sdt" (cancel maintenance), "get_sdt" (details).

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.

Tool Definition Quality

A4.9/5.0
Behavior5/5

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

Annotations already indicate readOnlyHint=true. Description adds value by explaining that SDTs suppress alerting during maintenance, describes return structure, and warns about negative total values indicating incomplete results. 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?

While longer, the description is well-structured with clear sections (returns, what are SDTs, when to use, filter patterns, types, best practice, important note, related tools). Front-loaded with main purpose. Slightly verbose but every sentence 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?

Despite no output schema, description fully documents return structure. Covers edge cases (negative total), best practices (meaningful comments), and common use cases. For a list tool with 5 parameters and no output schema, this is complete and self-contained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions for all 5 parameters. Description adds filter pattern examples (e.g., 'isEffective:true') and clarifies autoPaginate behavior beyond schema, providing meaningful additional context.

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 Scheduled Down Times (SDTs) in LogicMonitor (LM) monitoring.' It uses a specific verb+resource combination and explains what SDTs are, distinguishing it from sibling tool 'get_sdt' which retrieves a single 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 with five specific scenarios (view active, check upcoming, verify creation, etc.), common filter patterns, SDT types explained, and related tools. This gives comprehensive guidance on when to use this tool vs 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