Skip to main content
Glama
monitoringartist

LogicMonitor MCP Server

list_configsources

Read-only

List all ConfigSources in LogicMonitor to discover configuration tracking, find specific configs, and audit monitoring coverage for compliance and change management.

Instructions

List all ConfigSources in LogicMonitor (LM) monitoring.

Returns: Array of ConfigSources with: id, name, displayName, description, appliesTo logic, collection method.

What are ConfigSources: Track configuration file changes for compliance and change management. Similar to datasources, but for configs instead of metrics. Alert when configs change unexpectedly.

When to use:

  • Find ConfigSource for specific resource/device type (e.g., Cisco_IOS_Config)

  • Discover what configs are being tracked

  • Get ConfigSource IDs for API operations

  • Audit configuration monitoring coverage

What configs can be tracked:

  • Network resources/devices: Router configs, switch configs, firewall rules

  • Linux: /etc files, app configs, SSH authorized_keys

  • Windows: Registry keys, security policies

  • Cloud: Security groups, IAM policies

Use cases:

  • Compliance: "Alert when firewall rules change"

  • Change management: "Who modified this router config?"

  • Rollback: Compare current config to previous version

  • Audit: "Show all config changes in last 30 days"

Common ConfigSources:

  • Cisco_IOS_Config: Cisco router/switch configs

  • F5_LTM_Config: F5 load balancer configs

  • Palo_Alto_Config: Palo Alto firewall rules

  • Linux_Config_Files: Monitor /etc files

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: "get_configsource" (details), "list_device_configs" (see configs for device).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
Behavior4/5

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

ReadOnlyHint is true, description adds context about pagination behavior (negative total indicates incomplete results) and autoPaginate. No contradictions, but could disclose more about authentication or rate limits.

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, front-loaded with main purpose. Slightly verbose but each section adds value, so earns its place.

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 explicitly states return format (Array with fields), covers common use cases, examples of ConfigSources, and even alerts about negative total. Very complete.

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 baseline is 3. Description adds value by explaining the autoPaginate behavior and the negative total hint for pagination, which is beyond schema.

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?

Description clearly states 'List all ConfigSources in LogicMonitor (LM) monitoring' and explains what ConfigSources are. Distinguishes from sibling tools like get_configsource and list_device_configs.

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?

Provides explicit when-to-use scenarios (find ConfigSource for specific resource, discover configs, get IDs, audit coverage) and mentions related tools at the end.

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