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

io.github.ryanmat/logicmonitor

by ryanmat

get_devices

Read-onlyIdempotent

Retrieve LogicMonitor devices with optional filters by name, hostname, status, or device group, plus pagination for large inventories.

Instructions

List devices (resources) from LogicMonitor, optionally filtered by name, hostname, status or device group

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (max 1000)
filterNoRaw filter expression (overrides other filters). Syntax: field:value, field~value. String values must be quoted: displayName~"server". Custom property queries use dot-notation: customProperties.name:"env",customProperties.value:"prod"
offsetNoPagination offset
statusNoFilter by device status
group_idNoFilter by device group ID
name_filterNoFilter by display name (substring match)
hostname_filterNoFilter by hostname or IP address (substring match)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.2.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety is well covered structurally. The description adds only the notion that filters are optional; it says nothing about return volume, pagination defaults, or how the raw filter interacts with the named filters beyond what the schema states.

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?

A single front-loaded sentence naming the verb, resource, system and filter surface with no filler. It could be marginally stronger by naming the scoping alternative, but nothing is wasted.

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?

With seven optional parameters and no output schema, the definition is adequate because the input schema is fully self-documenting. However, nothing is said about the shape or volume of results an agent should expect when calling an unfiltered list.

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 every parameter, including the raw filter syntax and enum values, is documented in the schema itself. The description's enumeration of filter dimensions mirrors the schema without adding meaning, 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?

States a specific verb ('List') and resource ('devices (resources) from LogicMonitor') plus the optional filter dimensions, which is clear enough to act on. It does not distinguish this general listing from siblings like get_unmonitored_devices or get_datasource_devices, so it stops 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 word 'optionally filtered by name, hostname, status or device group' implies a general-purpose listing, but there is no explicit when-to-use or when-not-to-use guidance and no pointer to the narrower device siblings. Usage is inferable rather than directed.

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