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

io.github.ryanmat/logicmonitor

by ryanmat

get_alert_settings

Read-onlyIdempotent

Read the alert thresholds in force for a datapoint at instance, device, or group level, including the level and global threshold that apply, before tuning a noisy threshold.

Instructions

Read datapoint alert thresholds at instance, device or group level: each datapoint's threshold in force and the level it comes from (instance, instance_group, device_datasource, device_group with source_group, group or global), beside the level's own and the global threshold. Use it before tuning a noisy threshold with update_alert_settings.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "level": "<level>"
    },
    "name": "get_alert_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelYesinstance: one device datasource instance (device_id, device_datasource_id, instance_id); device: every instance on device_id; group: a device group's settings for one datasource (group_id, datasource_id)
limitNoMax results
offsetNoPagination offset
group_idNoDevice group ID (group level)
device_idNoDevice ID (instance and device level)
instance_idNoInstance ID (instance level)
datapoint_idNoOne datapoint's setting (instance level)
datasource_idNoDatasource ID (group level)
device_datasource_idNoDevice datasource ID, as get_device_datasources lists it (instance level)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this a read-only, idempotent, non-destructive operation, so the safety profile is covered. The description adds genuinely useful behavior beyond that: it explains that thresholds are resolved through an inheritance chain (instance, instance_group, device_datasource, device_group, group, global) and reports both the effective and the level-own, global values. It stops short of describing pagination or result shape, but that is minor given the safety hints.

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?

Two sentences with the capability front-loaded and the actionable guidance second; nothing is filler. The long parenthetical enumeration of source levels is dense but each item carries information about the threshold hierarchy.

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?

With nine parameters and no output schema, the description does the necessary work of describing what comes back (in-force threshold, its source level, the level's own and global threshold). That is close to complete; only pagination behavior and the exact response object remain unstated.

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 the baseline is 3, and the description earns a bump by explaining what the returned 'level it comes from' values mean, which contextualizes the level enum and the per-level ID parameters. It does not add anything about limit/offset, but those are already self-documented.

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 opens with a specific verb and resource ('Read datapoint alert thresholds') and scopes it to three levels (instance, device, group), which separates it from broader alert-rule readers like get_alert_rules. It does not name any read sibling explicitly, so the differentiation is implied rather than stated.

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

Usage Guidelines4/5

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

'Use it before tuning a noisy threshold with update_alert_settings' gives a concrete workflow trigger and names the follow-up tool. There is no explicit when-not guidance or statement of prerequisites, but the context for use is unambiguous.

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