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

io.github.ryanmat/logicmonitor

by ryanmat

get_device_group_properties

Read-onlyIdempotent

Retrieve a device group's own, inherited, and system properties with effective values, types, and ancestor sources. Use it to read one property or list all properties for a group.

Instructions

Get a device group's (resource group's) properties: its own, the ones it inherits and the system ones, each with the value in force, its type (custom, inherit or system) and the ancestor groups that hold the same name, nearest first; an inherited value is the nearest one's. property_name reads one property.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "group_id": "<group_id>"
    },
    "name": "get_device_group_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results
offsetNoPagination offset
group_idYesDevice group ID
name_filterNoFilter by property name (substring match)
property_nameNoRead only this property

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and openWorld, so the description earns credit for going further: it explains that inherited values resolve to the nearest ancestor's value and that ancestors are returned nearest first, which is real behavioral detail an agent cannot get from structured fields. It does not discuss pagination interaction or result size, but that gap is modest for a read-only operation.

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 front-loaded sentence establishes the resource and expands into the result shape, with no filler. The nested parentheticals and semicolon-chained clauses make it dense to parse, but every clause carries information.

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 carries the burden of describing return values, and it does so well — value in force, type of origin, and ancestor chain with ordering. For a five-parameter read-only tool this is nearly complete; only guidance on choosing between this and sibling property tools is missing.

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%, so all five parameters are already documented, which sets the baseline at 3. The description adds slight meaning by clarifying that property_name restricts the call to a single property read, but says nothing extra about limit, offset, or name_filter beyond what the schema states.

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 uses a specific verb+resource (get a device group's properties) and enumerates exactly what comes back: own, inherited, and system properties, each with value, type, and owning ancestors. It is clear, though it never contrasts itself with the adjacent get_device_properties or get_device_property, so disambiguation rests on the group-vs-device noun alone.

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 only implied: the closing note that 'property_name reads one property' signals a narrowing mode, and name_filter/limit/offset imply bulk listing, but there is no explicit statement of when to choose this over a sibling property-retrieval tool or when the single-property mode is preferable.

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