Skip to main content
Glama
monitoringartist

LogicMonitor MCP Server

list_eventsources

Read-only

Lists all EventSources to discover log monitoring configurations and audit event collection across Windows, Linux, and network resources.

Instructions

List all EventSources in LogicMonitor (LM) monitoring.

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

What are EventSources: Collect and process event data (logs, Windows events, syslog, traps). Different from DataSources (metrics) and ConfigSources (configs). Used for log monitoring and event correlation.

When to use:

  • Find EventSource for log monitoring

  • Discover what events are being collected

  • Get EventSource IDs for operations

  • Audit event monitoring coverage

Event types collected:

  • Windows Event Logs: Application, Security, System logs

  • Syslog: Linux/Unix system logs, network resource/device logs

  • SNMP Traps: Network resource/device alerts and notifications

  • Application logs: Custom app logs, web server logs

  • Cloud events: CloudWatch logs, Azure events

Common EventSources:

  • Windows_Application_EventLog: Windows application events

  • Windows_Security_EventLog: Security/audit logs

  • Linux_Syslog: Linux system logs via syslog

  • SNMP_Traps: Network resource/device SNMP traps

  • VMware_Events: vCenter events

Use cases:

  • Monitor Windows failed login attempts

  • Alert on ERROR/CRITICAL in application logs

  • Collect network resource/device syslog for troubleshooting

  • Track security events for compliance

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_eventsource" (details), "list_device_eventsources" (events 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.
Behavior5/5

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

Annotations only have readOnlyHint=true. Description adds rich behavioral details: warns about negative total indicating incomplete results, explains pagination behavior, lists return fields (id, name, displayName, etc.), and provides examples of EventSources. 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is lengthy but well-structured with clear sections (Returns, What are, When to use, Event types, Common, Use cases, Important, Related tools). Some redundancy; could be more concise without losing information.

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?

Covers all aspects: purpose, usage, common EventSources, event types, pagination warning, filter examples, and related tools. No output schema, but description lists return fields. Complete for a list tool with 5 parameters.

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% for all 5 parameters. Description adds value by explaining pagination implications ('use pagination...or set autoPaginate: true') and giving examples of filter expressions. This goes beyond baseline 3.

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 states 'List all EventSources in LogicMonitor (LM) monitoring' with clear verb and resource. It explains what EventSources are and distinguishes them from DataSources and ConfigSources. Differentiates from sibling tools 'get_eventsource' and 'list_device_eventsources'.

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?

Explicit 'When to use' bullet points (find EventSource, discover events, get IDs, audit coverage). Mentions related tools for details and device-specific listing. Does not explicitly state when not to use, but context is clear.

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