Skip to main content
Glama
monitoringartist

LogicMonitor MCP Server

get_resource_instance_data

Read-only

Fetch time-series metrics like CPU, memory, or disk usage for a specific resource instance in LogicMonitor. Specify datapoints and time range to get data with timestamps and values.

Instructions

Get time-series metrics/datapoints data (e.g., CPU/memory/network utilization) for a specific resource/device datasource instance in LogicMonitor (LM) monitoring.

Returns: Time-series data with timestamps and values for requested datapoints. Format: {timestamps: [epoch1, epoch2], values: {datapoint1: [val1, val2], datapoint2: [val1, val2]}}.

When to use:

  • Get CPU utilization for last 24 hours

  • Fetch disk usage trends

  • Retrieve network bandwidth data

  • Export metrics for analysis

  • Build custom dashboards/reports

Required workflow (3 steps):

  • Use "list_resource_datasources" → get deviceDataSourceId for datasource (e.g., WinCPU)

  • Use "list_resource_instances" → get instanceId for specific instance (e.g., CPU Core 0)

  • Use this tool → get actual metric values for that instance

Parameters:

  • deviceId: Device ID from "get_resource" or "list_resources"

  • deviceDataSourceId: From "get_resource_datasource" or "list_resource_datasources"

  • instanceId: From "list_resource_instances"

  • datapoints: Comma-separated metric names (e.g., "CPUBusyPercent,MemoryUsedPercent")

  • start/end: Time range in epoch milliseconds (not seconds!), start time must be before current time

Example: Get last hour CPU data: start=Date.now()-3600000, end=Date.now()

Time range tips: If omitted, returns last 2 hours. Max range: 1 year. Use shorter ranges for better performance.

Related tools: "list_resource_datasources", "list_resource_instances".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deviceIdYesThe resource/device ID
deviceDataSourceIdYesThe resource/device datasource ID
instanceIdYesThe instance ID
datapointsNoComma-separated list of metric/datapoint names
startNoStart time (epoch milliseconds), start time must be before current time
endNoEnd time (epoch milliseconds)
formatNoResponse format: "json" or "csv"
Behavior5/5

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

Annotations indicate readOnlyHint=true; description adds output format, default time range (last 2 hours), max range (1 year), and example. No contradictions.

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?

Well-structured with clear sections and front-loaded purpose. Slightly verbose but every sentence adds value. Could trim some examples but remains effective.

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?

No output schema, but description details the return format. Covers the prerequisite workflow, time range behavior, and parameter usage. Complete for the tool's complexity.

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

Parameters5/5

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

All 7 parameters are documented in schema. Description adds value by explaining datapoints as comma-separated, start/end in epoch milliseconds with a note to avoid seconds, and a concrete example. Time range tips further clarify behavior.

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?

Clearly states it gets time-series metrics/datapoints for a resource instance. Distinguishes from sibling list/get tools by focusing on metric values, with examples like CPU utilization and disk usage.

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

Usage Guidelines5/5

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

Explicitly provides usage scenarios (e.g., 'Get CPU utilization for last 24 hours') and a required 3-step workflow involving list_resource_datasources and list_resource_instances. Also mentions time range tips and related tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/monitoringartist/logicmonitor-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server