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

io.github.ryanmat/logicmonitor

by ryanmat

portal_overview

Read-onlyIdempotent

Summarizes recent LogicMonitor portal alerts, clusters, collectors, and active SDTs for shift handoff; full detail adds open critical/error alerts and dead devices.

Instructions

Shift-handoff overview of the portal: reads the alert window of the last hours_back hours once for statistics, clusters and noise, and lists the collectors and the active SDTs. alert_clusters lists the five largest clusters of each type with ten alert ids each, and its cluster_count and by_type count them all. detail_level=full adds up to 20 open critical and 20 open error alerts from across the portal, not only the window, and up to 20 dead devices; summary does not read them.

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": "portal_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
hours_backNoHours to look back (default: 4)
detail_levelNoOutput detail level (default: summary)summary

Output Schema

NameRequiredDescriptionDefault
noiseYesanalyze_alerts 'noise'.
portalNoThe portal the call ran against, in multi-portal mode.
warningsNo
collectorsYesget_collectors' first page.
hours_backYesHours the alert window reaches back.
active_sdtsYesget_active_sdts' first page.
dead_devicesNoFull: up to 20 dead devices (get_devices status=dead).
detail_levelYes
error_alertsNoFull: up to 20 open error alerts, portal-wide (get_alerts).
alert_clustersYesanalyze_alerts 'clusters'.
critical_alertsNoFull: up to 20 open critical alerts, portal-wide (get_alerts).
alert_statisticsYesanalyze_alerts 'statistics'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv5.0.1
    • removedInput schema / properties / summarize
      Removed value: -{
      -  "default": false,
      -  "description": "Append plain-English NL summary via IBM Granite (requires WATSONX_API_KEY)",
      -  "type": "boolean"
      -}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "active_sdts": {
      +      "description": "get_active_sdts' first page.",
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "alert_clusters": {
      +      "description": "analyze_alerts 'clusters'.",
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "alert_statistics": {
      +      "description": "analyze_alerts 'statistics'.",
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "collectors": {
      +      "description": "get_collectors' first page.",
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "critical_alerts": {
      +      "description": "Full: up to 20 open critical alerts, portal-wide (get_alerts).",
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "dead_devices": {
      +      "description": "Full: up to 20 dead devices (get_devices status=dead).",
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "detail_level": {
      +      "enum": [
      +        "summary",
      +        "full"
      +      ],
      +      "type": "string"
      +    },
      +    "error_alerts": {
      +      "description": "Full: up to 20 open error alerts, portal-wide (get_alerts).",
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "hours_back": {
      +      "description": "Hours the alert window reaches back.",
      +      "type": "integer"
      +    },
      +    "noise": {
      +      "description": "analyze_alerts 'noise'.",
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "portal": {
      +      "description": "The portal the call ran against, in multi-portal mode.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "warnings": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "hours_back",
      +    "detail_level",
      +    "alert_statistics",
      +    "alert_clusters",
      +    "noise",
      +    "collectors",
      +    "active_sdts"
      +  ],
      +  "type": "object"
      +}
  2. First observedv4.2.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the alert window is read only once, detail_level=full pulls up to 20 open critical + 20 open error alerts from across the portal (outside the window) plus up to 20 dead devices, and summary skips those reads, which signals a meaningful cost/volume difference.

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?

It is front-loaded with the overview purpose and stays to three dense sentences with no filler. The middle sentence detailing cluster contents and count fields is somewhat over-specified given an output schema exists, but it is not padding.

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?

For a 2-parameter, read-only, output-schema-backed overview tool, the description is sufficient: both parameters are characterized, the scope difference between windowed and portal-wide data is clear, and caps on returned entities are stated.

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 both parameters are already documented and the baseline would be 3. The description goes beyond the enum labels by explaining what summary versus full actually fetches, and confirms that hours_back scopes the alert window — a real semantic addition rather than a restatement.

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 names a specific resource (shift-handoff overview of the portal) and enumerates exactly what it aggregates: alert statistics/clusters/noise, collectors, and active SDTs. That distinguishes it from the granular get_alerts/get_collector/get_active_sdts siblings, though it never names those alternatives explicitly.

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 'shift-handoff overview' framing implies a context (a periodic high-level check-in rather than an investigation), but there is no explicit when-to-use or when-not-to-use statement, and no routing to the narrower sibling tools for follow-up.

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