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

io.github.ryanmat/logicmonitor

by ryanmat

get_device_instances

Read-onlyIdempotent

Retrieve instances of a datasource on a device to inspect resource-level monitoring data, with optional name filtering and pagination.

Instructions

Get instances of a datasource on a device (resource)

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>",
      "device_datasource_id": "<device_datasource_id>"
    },
    "name": "get_device_instances"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results
offsetNoPagination offset
device_idYesDevice ID
name_filterNoFilter by instance name (substring match)
device_datasource_idYesDevice-DataSource ID (from get_device_datasources)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv5.0.1
    • addedInput schema / properties / name_filter
      Added value: +{
      +  "description": "Filter by instance name (substring match)",
      +  "type": "string"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "default": 0,
      +  "description": "Pagination offset",
      +  "type": "integer"
      +}
  2. First observedv4.2.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered. The description adds no behavioral context beyond that — nothing about pagination defaults, result size, or what an 'instance' represents. With annotations carrying the burden, the description still fails to add anything of its own.

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 short, front-loaded sentence with no filler. It is efficient, though the dangling parenthetical '(resource)' is more confusing than clarifying and could be dropped.

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?

The tool takes 5 parameters with 2 required, has no output schema, and relies on rich annotations plus a fully described schema. Given that, the description is minimally sufficient but omits what an 'instance' is and how results relate to get_device_datasources, which is the main open question for correct invocation.

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%, with limit, offset, device_id, name_filter and device_datasource_id all documented inline. The description adds no extra meaning about filtering or pagination semantics, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Get instances of a datasource on a device'), so the core action is recoverable. However, the trailing '(resource)' is ambiguous, and it gives no signal about how 'instances' differ from the sibling get_device_datasources or get_device_data, leaving an agent to guess which endpoint to call.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no stated prerequisites, and no mention of alternatives among the many get_device_* siblings. The only routing hint (that device_datasource_id comes from get_device_datasources) lives in the input 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