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

io.github.ryanmat/logicmonitor

by ryanmat

get_device_property

Read-onlyIdempotent

Retrieve a specific device property to inspect its value, type (custom, inherit, auto, or system), and the groups or property rules that provide it.

Instructions

Get a specific property of a device (resource): its value, its type (custom, inherit, auto or system) and sources, the groups and property rules the portal lists for that name, with the value each holds.

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": {
      "device_id": "<device_id>",
      "property_name": "<property_name>"
    },
    "name": "get_device_property"
  }
}

Input Schema

NameRequiredDescriptionDefault
device_idYesDevice ID
property_nameYesProperty name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.2.0

TDQS

A3.5/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 covered. The description contributes genuinely new behavioral detail by defining the return shape and the type taxonomy (custom, inherit, auto, system) plus the meaning of `sources`. It stops short of stating what happens when the device or property name does not exist, which matters for an open-world lookup tool.

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 dense sentence with no filler; the resource and its returned fields are front-loaded. The trailing parenthetical and nested clause about `sources` make it slightly harder to parse than necessary, but nothing is redundant.

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 must carry the return-value burden, and it does: value, type taxonomy, and source groups/rules are all named. Combined with annotations covering the safety profile and a fully documented two-parameter schema, the definition is close to self-sufficient, missing only failure behavior.

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%, so both parameters are already documented, and the description rightly does not restate them. It adds only marginal meaning, notably that `property_name` is matched against the groups and property rules "the portal lists for that name", which hints at lookup scope but not at format or case sensitivity.

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 and resource ("Get a specific property of a device") and even enumerates what comes back: value, type, and `sources`. It is clearly distinct from a list-all tool, but it never names the sibling `get_device_properties`, so the agent must infer the singular-vs-plural split from names 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 word "specific" hints that this is for one named property rather than a full property dump. There is no explicit when-to-use statement, no prerequisite (e.g., that the device must exist), and no pointer to `get_device_properties` as the alternative for enumerating all properties.

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