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

io.github.ryanmat/logicmonitor

by ryanmat

get_datasource_devices

Read-onlyIdempotent

List devices a datasource applies to, including up to 10 instances per device and a flag when more instances exist. Filter by device name and paginate results.

Instructions

List the devices/resources a datasource applies to, each with up to 10 of its instances; more_instances says it has others, which get_device_instances lists.

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": {
      "datasource_id": "<datasource_id>"
    },
    "name": "get_datasource_devices"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results
offsetNoPagination offset
name_filterNoFilter by device display name (substring match)
datasource_idYesDatasource ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and open-world, so safety is covered by structured data. The description contributes genuinely new behavior: each device returns at most 10 instances and a more_instances flag signals truncation, which the agent cannot infer from annotations. It leaves unclear whether limit/offset paginate devices or instances, which is the one behavioral gap.

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?

A single sentence with no waste, front-loaded with verb and scope before the behavioral caveat about instance truncation. The semicolon clause carries real information (the more_instances flag and its follow-up tool) rather than filler.

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 return-value burden and does explain the nested structure (devices each with instances) plus the truncation flag. It is nearly complete for a filtered-list tool; only the pagination semantics of limit/offset relative to the per-device instance cap remain ambiguous.

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 all four parameters (datasource_id, limit, offset, name_filter) are already documented in the schema. The description adds no syntax, default, or interaction detail for them, and the relationship between the '10 instances' cap and the limit parameter is not clarified. Baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource ('List the devices/resources a datasource applies to') and immediately discloses the shape of the result, including the 10-instance cap per device. The closing clause names the sibling get_device_instances and what it covers, so an agent can separate the two tools without opening either schema.

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

Usage Guidelines4/5

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

Clear context for use: this is the entry point for enumerating devices attached to a datasource, and the description routes the agent to get_device_instances when the truncated instance list is insufficient. It stops short of stating exclusions (e.g., when to prefer get_devices for org-wide listings), so it is clear but not fully explicit about alternatives.

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