Skip to main content
Glama
io.github.ryanmat/logicmonitor

io.github.ryanmat/logicmonitor

by ryanmat

get_eventsource

Read-onlyIdempotent

Retrieve details for a specific LogicMonitor EventSource by ID, optionally returning the full REST object instead of the summary.

Instructions

Get details about a specific EventSource

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "eventsource_id": "<eventsource_id>"
    },
    "name": "get_eventsource"
  }
}

Input Schema

NameRequiredDescriptionDefault
rawNoReturn the full REST object, the definition create_eventsource takes, instead of the summary
eventsource_idYesEventSource ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.0.1
    • addedInput schema / properties / raw
      Added value: +{
      +  "default": false,
      +  "description": "Return the full REST object, the definition create_eventsource takes, instead of the summary",
      +  "type": "boolean"
      +}
  2. First observedv4.2.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered structurally. The description adds no behavior beyond that — nothing about what 'details' includes, whether the summary vs. raw form differs materially, or about auth/rate limits — leaving the annotations to carry the whole burden.

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?

It is a single front-loaded sentence with no wasted wording, but that brevity comes at the cost of substance — there is essentially only a restatement of the name plus the resource.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a simple read-only single-entity fetch with full schema coverage and rich annotations, and no output schema, so the description needn't explain return values. Still, 'details' is left undefined and the meaning of the summary-vs-raw distinction relative to what create_eventsource accepts is never connected, leaving a modest gap.

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 description coverage is 100%, and the raw flag already carries its own explanation ('Return the full REST object, the definition create_eventsource takes, instead of the summary'). The description contributes nothing further, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource — 'Get details about a specific EventSource' — so an agent immediately knows it retrieves a single entity by identifier. It does not, however, distinguish this from neighboring lookups such as get_configsource or get_collectors, so an agent must infer the choice from resource names alone.

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

Usage Guidelines2/5

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

There is no guidance on when to call this versus the plural list-style siblings, and no stated prerequisites or exclusions. The only implicit cue is the required eventsource_id, which signals a single-record lookup.

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

Deploy Server

Other Tools