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

io.github.ryanmat/logicmonitor

by ryanmat

get_unmonitored_devices

Read-onlyIdempotent

Lists NetScan-discovered devices and resources that are not monitored, with pagination, to help identify monitoring gaps and onboard them.

Instructions

List the portal's unmonitored devices/resources, found by a NetScan and not monitored, rows as the API returns 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": "get_unmonitored_devices"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results
offsetNoPagination offset

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

B3.4/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 fully covered. The description adds only 'rows as the API returns them', a weak hint that no normalization is applied; it says nothing about result volume, ordering, or what happens when no NetScan has run.

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?

One compact sentence with the qualifier front-loaded. It is slightly redundant ('unmonitored ... and not monitored'), but there is no filler or boilerplate.

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

Completeness3/5

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

For a simple read-only list tool with annotations covering safety and a fully described two-parameter schema, most of the burden is carried elsewhere. However, the return shape is described only vaguely and the device-vs-resource distinction within the result rows is never clarified, which matters since there is no output schema.

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 both parameters (limit, offset) are documented in the schema itself, so baseline 3 applies. The description adds no additional meaning such as default page size behavior, max limits, or whether offset pagination is stable.

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?

Uses a specific verb+resource ('List ... unmonitored devices/resources') and narrows the scope with 'found by a NetScan and not monitored', which is a real semantic qualifier rather than a restatement of the name. It does not name or contrast with the obvious sibling get_devices, so it falls short of a 5.

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 'found by a NetScan and not monitored' implies the use case (find discovered-but-unmanaged assets), but there is no explicit when-to-use or when-not-to-use guidance and no mention of how this differs from get_devices or get_datasource_devices.

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