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

io.github.ryanmat/logicmonitor

by ryanmat

get_diagnostic_remediation_assignments

Read-onlyIdempotent

List diagnostic and remediation modules assigned to a specific alert or resource, resolving which Automated Diagnostics & Remediation sources actually apply to that target.

Instructions

List the diagnostic and remediation sources assigned to a specific resource or alert (Automated Diagnostics & Remediation). Unlike get_diagnosticsources/get_remediationsources, this resolves which modules actually apply to the target.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results
alert_idNoAlert ID (provide this or resource_id)
module_typeNoRestrict to one module type (both if omitted)
resource_idNoDevice/resource ID (provide this or alert_id)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.0.1
    • changedInput schema / properties / module_type / enum
      Previous value: -[
      -  "diagnosticsource",
      -  "remediationsource"
      -]New value: +[
      +  "diagnostic",
      +  "remediation"
      +]
  2. First observedv4.2.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so the safety profile is covered. The description adds the semantic nuance that results are target-scoped rather than catalog-wide, but says nothing about what happens if neither alert_id nor resource_id is supplied, nor about result ordering or paging beyond the limit parameter.

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?

Two tight sentences with no filler; the core action is stated first and the sibling disambiguation follows immediately.

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 read-only list tool with a fully documented four-parameter schema and no output schema, this is close to sufficient. The main omission is the shape of the returned assignments and behavior when neither selector is provided, which an agent would otherwise have to discover by calling it.

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 coverage is 100% and every parameter already has inline documentation including the alert_id/resource_id either-or rule and the module_type default (both). The description only reinforces the target-scoping concept, adding little beyond what the schema states.

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?

States a specific verb and resource ('List the diagnostic and remediation sources assigned to a specific resource or alert') and adds the parenthetical feature area. It also names the sibling tools it is not, so an agent can separate it from the catalog-listing tools without opening a schema.

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?

Explicitly contrasts itself with get_diagnosticsources/get_remediationsources ('this resolves which modules actually apply to the target'), giving a clear selection rule. It does not explicitly state when to prefer those siblings instead, so the routing is one-directional rather than fully closed.

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