Skip to main content
Glama
io.github.ryanmat/logicmonitor

io.github.ryanmat/logicmonitor

by ryanmat

get_upcoming_sdts

Read-onlyIdempotent

Retrieve scheduled downtime (SDT) records that start within a chosen time window, with offset and limit controls for pagination.

Instructions

Get SDTs scheduled to start within a time window

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_upcoming_sdts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results
offsetNoPagination offset
hours_aheadNoHours ahead to look

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.0.1
    • addedInput schema / properties / offset
      Added value: +{
      +  "default": 0,
      +  "description": "Pagination offset",
      +  "type": "integer"
      +}
  2. First observedv4.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds only the time-window scoping; it says nothing about pagination behavior, whether results are sorted, or how an empty window is returned.

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

Conciseness5/5

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

A single short sentence with the scope front-loaded and zero filler. Every word carries information and nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple, fully-optional read tool with complete schema coverage and rich annotations, this is nearly sufficient. The main residual gap is that 'SDT' is unexplained jargon, so an agent unfamiliar with the domain must infer what resource is being returned.

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 description coverage is 100%, and all three parameters carry inline descriptions and defaults, so the schema already does the heavy lifting. The description reinforces the meaning of hours_ahead via 'within a time window' but adds no format or boundary detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get SDTs') plus a clear scope ('scheduled to start within a time window'), which implicitly separates it from the active-SDT sibling. However, the acronym 'SDT' is never expanded, and no sibling is named explicitly, so differentiation relies on the agent inferring the active-vs-upcoming contrast.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'scheduled to start within a time window' implies the use case (forward-looking scheduling rather than current downtime), but there is no explicit when-to-use statement, no mention of when to prefer get_active_sdts or get_sdts, and no stated exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools