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

io.github.ryanmat/logicmonitor

by ryanmat

get_sdts

Read-onlyIdempotent

List scheduled downtimes from LogicMonitor and filter by admin, SDT type, device, or device group to identify maintenance windows.

Instructions

List scheduled downtimes from LogicMonitor

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_sdts"
  }
}

Input Schema

NameRequiredDescriptionDefault
adminNoFilter by admin username (substring match)
limitNoMax results
filterNoRaw filter expression (overrides other filters). Example: type:DeviceSDT,admin~john
offsetNoPagination offset
sdt_typeNoFilter by SDT type
device_idNoFilter by device ID
device_group_idNoFilter by device group ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

C2.9/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds no behavioral context beyond the annotations—it does not mention pagination defaults, filter override behavior, or the scope of results relative to the active/upcoming siblings.

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?

The description is a single front-loaded sentence with no wasted words. It is arguably too terse for a tool with seven parameters and three related sibling tools, but it is structurally clean.

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

Completeness2/5

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

For a list tool with seven optional filter and pagination parameters, the description says nothing about result scope, filtering behavior, or how it relates to get_active_sdts and get_upcoming_sdts. The annotations and full schema coverage lower the bar, but the missing scope distinction is a meaningful gap.

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%, so every parameter is already documented in the input schema, including the enum for sdt_type and the override behavior of filter. The description adds no additional meaning beyond the schema, so the baseline of 3 is appropriate.

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?

The description states a specific verb and resource: 'List scheduled downtimes from LogicMonitor.' An agent can tell this is a read/list operation for SDTs, but the wording gives no clue how it differs from the sibling tools get_active_sdts and get_upcoming_sdts, which cover overlapping scopes.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no mention of alternatives. Given that get_active_sdts and get_upcoming_sdts exist as siblings, the agent is left to infer whether this tool returns all SDTs, only future ones, or something else.

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