Skip to main content
Glama
monitoringartist

LogicMonitor MCP Server

list_resource_datasources

Read-only

List datasources monitoring a specific LogicMonitor resource, showing status, instance count, and alert status. Get deviceDataSourceId for metric retrieval.

Instructions

List datasources applied to a specific resource/device in LogicMonitor (LM) monitoring.

Returns: Array of datasources actively monitoring this resource/device with: id (deviceDataSourceId), dataSourceName, dataSourceDisplayName, status, alert status, instance count, last poll time.

When to use:

  • See what's being monitored on a resource/device

  • Verify datasource is collecting data

  • Get deviceDataSourceId for metric retrieval

  • Troubleshoot missing data

  • Check datasource health

What you discover:

  • Which datasources are active (e.g., WinCPU, WinMemory, SNMP_Network_Interfaces)

  • How many instances per datasource (e.g., 3 disks, 4 network interfaces)

  • Collection status: Collecting data vs errors

  • Alert status: Any active alerts from this datasource

This is step 1 for getting metrics: Complete workflow to retrieve metric data: 1. Use this tool → get deviceDataSourceId for datasource you want (e.g., WinCPU) 2. Use "list_device_instances" → get instanceId for specific instance 3. Use "get_device_instance_data" → get actual metric values

Troubleshooting use cases:

  • "Why no CPU data?" → Check if WinCPU datasource is applied and collecting

  • "Find disk datasource" → Look for datasource with "disk" or "volume" in name

  • "Check datasource errors" → Review status field for error messages

Important: A negative "total" value in the response indicates incomplete results. Use pagination (size/offset parameters) or set autoPaginate: true to retrieve all items.

Related tools: "list_device_instances" (next step), "get_device_instance_data" (get metrics), "update_device_datasource" (enable/disable).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deviceIdYesThe resource/device ID
sizeNoNumber of results per page (default: 50, max: 1000).
offsetNoStarting offset for pagination (default: 0). Use this to skip a specific number of results.
autoPaginateNoAutomatically fetch all pages (default: false). When true, fetches all results across multiple pages. When false, returns only the requested page. Use false for large result sets to avoid long response times.
filterNoFilter expression using LogicMonitor query syntax. Examples: name:*prod*, displayName~*server*, id>100, hostStatus:normal. Available operators: : (equals), ~ (includes), !: (not equals), !~ (not includes), >: (greater than or equals), <: (less than or equals), > (greater than), < (less than). Multiple conditions: Use comma (,) for AND, use || for OR. Do NOT use &&.
fieldsNoComma-separated list of fields to include in response. Examples: "id,displayName,hostStatus" or use "*" for all fields. Omit this parameter to receive a curated set of commonly used fields.
Behavior5/5

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

Annotations declare readOnlyHint=true, and description adds critical behavioral details: negative total indicates incomplete results, pagination behavior described, and return fields listed. No contradiction.

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 sections (When to use, What you discover, Workflow, Troubleshooting, Important). Each section earns its place, but the description is slightly lengthy; could be more concise.

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?

Given no output schema, description compensates by detailing return fields. Covers pagination, filtering, troubleshooting, and workflow. Context from siblings shows this tool is unique for listing datasources on a resource.

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% (all params described). Description adds context beyond schema: autoPaginate behavior, filter syntax with examples, fields parameter usage. Does not cover every nuance but adds significant value.

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?

The description clearly states the verb and resource: 'List datasources applied to a specific resource/device'. It distinguishes from sibling tools like 'get_resource_datasource' (single) and other list tools (different entities).

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?

Includes a 'When to use' section with specific use cases and a workflow (step 1 for metrics). Mentions related tools but does not explicitly state when NOT to use this tool or alternatives beyond the workflow.

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