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

io.github.ryanmat/logicmonitor

by ryanmat

get_device_data

Read-onlyIdempotent

Retrieve raw metric samples for a device datasource instance, like CPU, memory, or disk usage, over a specified time range. Use device_datasource_id from get_device_datasources.

Instructions

Get the raw metric values (samples) of a device/resource datasource instance, such as CPU, memory or disk usage

Common mistakes: Returns the last hour unless start_time or end_time is given. Requires device_datasource_id (from get_device_datasources) not the datasource definition ID.

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>",
      "instance_id": "<instance_id>"
    },
    "name": "get_device_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_timeNoEnd time in epoch seconds (optional)
device_idYesDevice ID
datapointsNoComma-separated datapoint names (optional, all if omitted)
start_timeNoStart time in epoch seconds (optional)
instance_idYesInstance ID
device_datasource_idYesDevice-DataSource ID (from get_device_datasources)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.2.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds behavior the annotations cannot: the implicit one-hour default window that silently truncates results, and the prerequisite that the datasource ID come from a different tool. It omits any note on result volume or pagination for large ranges, which is the remaining 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?

Two short paragraphs with the core purpose first and a 'Common mistakes' block that earns its place by covering the two most likely failure modes (wrong default window, wrong ID type). No filler or restatement of the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only metric-fetch tool with no output schema, six parameters at full schema coverage, and no nested objects, the description supplies what structured fields cannot: the default time window and the correct ID provenance. Nothing needed to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description still adds meaning beyond the schema by warning that device_datasource_id is not the datasource definition ID and by tying start_time/end_time to the last-hour default. The datapoints parameter is never mentioned in the description, so the added value is partial rather than exhaustive.

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 the raw metric values (samples) of a device/resource datasource instance', with examples (CPU, memory, disk usage) that pin down what a 'sample' is. It does not explicitly contrast itself with get_graph_data or get_website_data, so an agent must infer the boundary, but the resource is unambiguous.

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?

Gives concrete usage context: the default window is the last hour unless start_time/end_time are supplied, and device_datasource_id must be obtained from get_device_datasources rather than the datasource definition ID. It stops short of naming an alternative tool or stating when not to use it, so it lands at clear-context-without-exclusions.

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