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

io.github.ryanmat/logicmonitor

by ryanmat

audit_network_monitoring_coverage

Read-onlyIdempotent

Audit network monitoring coverage by counting onboarded UPS/PDU devices, interface DataSources, SNMP credentials, and NetFlow exporters, then return prioritized gaps with onboarding steps.

Instructions

Portal audit that counts UPS/PDU devices onboarded, interface DataSources applied, SNMP credentials configured, and NetFlow exporters set up. Returns a prioritized gap list, each gap with the onboarding step that would let the portal detect what it cannot detect today.

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

Input Schema

NameRequiredDescriptionDefault
group_idNoScope the audit to a device group. Omit for portal-wide.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.2.0

TDQS

A3.8/5.0
Behavior4/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 covered; the description adds genuine value by disclosing the return shape (a prioritized gap list, each gap paired with the remediation/onboarding step). That is meaningful context beyond structured fields, though it omits cost/latency expectations for a portal-wide open-world scan.

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 sentences, no filler, and the core scope ('Portal audit') plus the measured dimensions are front-loaded before the return-value sentence. Every clause contributes information about either what is counted or what comes back.

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 no output schema, the description correctly takes on the burden of explaining the return value (prioritized gap list with onboarding steps), and the single scoping parameter is documented in the schema. It would be complete at 5 with a note on whether the audit queries live portal state and how heavy that scan is, given openWorldHint=true.

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?

There is a single optional group_id parameter with 100% schema description coverage ('Scope the audit to a device group. Omit for portal-wide.'), so the schema already carries the semantics. The description adds nothing about the parameter and does not echo the portal-wide default, so the baseline of 3 applies.

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 gives a specific verb-resource pair ('Portal audit that counts UPS/PDU devices onboarded, interface DataSources applied, SNMP credentials configured, NetFlow exporters') and enumerates the exact dimensions measured, which sharply distinguishes it from log-style siblings such as get_audit_logs. It falls short of 5 only because it never names an alternative tool or explicitly frames itself against capacity/coverage siblings.

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?

Usage is implied rather than stated: an agent can infer the tool is for readiness/coverage assessment, but there is no 'use this when…' clause, no exclusions, and no mention of prerequisites such as the portal needing collectors or SNMP configured first. The only scoping guidance (group_id) lives in the schema, not the description.

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