Skip to main content
Glama
monitoringartist

LogicMonitor MCP Server

get_eventsource

Read-only

Retrieve complete details of an EventSource by ID to understand event collection, filter rules, severity mapping, and alert settings for troubleshooting and configuration review.

Instructions

Get detailed information about a specific EventSource by its ID in LogicMonitor (LM) monitoring.

Returns: Complete EventSource details: name, displayName, description, appliesTo logic, collection method, filter rules, severity mapping, alert settings.

When to use:

  • Understand what events are collected

  • Review filter rules (which events trigger alerts)

  • Check severity mapping

  • Troubleshoot event collection

  • See appliesTo logic

Key information:

  • appliesTo: Which resources/devicesget event monitoring

  • filters: Rules for parsing/matching events

  • severityMapping: Map event levels (INFO/WARN/ERROR) to LM alert levels

  • schedule: When event collection runs

Workflow: Use "list_eventsources" to find eventSourceId, then use this tool for complete configuration.

Related tools: "list_eventsources" (find EventSource), "list_device_eventsources" (events for device).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eventSourceIdYesThe ID of the eventsource to retrieve
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 already declare readOnlyHint=true, so agent knows it's safe. Description adds detail about what is returned (complete details, specific fields) and key information about response structure. 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.

Conciseness5/5

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

Description is well-structured with bold headers, bullet points, and front-loaded summary. Every section (Returns, When to use, Key information, Workflow, Related tools) provides unique value without redundancy.

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?

Despite no output schema, description fully explains return values (name, displayName, appliesTo, filters, etc.). Provides workflow context and related tools. All necessary information for a get tool is present.

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

Parameters3/5

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

Schema coverage is 100% with both parameters already described. Description does not add new parameter-level detail beyond the schema; it repeats fields but not in a way that increases understanding of parameter usage.

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 'Get detailed information about a specific EventSource by its ID', using a specific verb and resource. It distinguishes from siblings by listing related tools (list_eventsources, list_device_eventsources) and focusing on single item retrieval.

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 'When to use' section with bullet points covering scenarios like understanding events, reviewing filters, troubleshooting. Workflow guidance is given: use list_eventsources first. Alternatives are named.

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