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

io.github.ryanmat/logicmonitor

by ryanmat

get_collector_events

Read-onlyIdempotent

List a collector's recent events newest first—agent/sbproxy restarts, credential rotation, and unreachable reports with time and build—to review history; use collector health for current state.

Instructions

List one collector's events, newest first: agent and sbproxy restarts, credential rotation, and reports that the collector is unreachable, each with its time and build. Use it for a collector's recent history; get_collector_health gives its current state.

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": {
      "collector_id": "<collector_id>"
    },
    "name": "get_collector_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results
offsetNoPagination offset
collector_idYesCollector ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

A4.7/5.0
Behavior4/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. The description still adds real value beyond them by disclosing result ordering ('newest first') and the concrete event categories and fields (time, build) that will be returned. It stops short of noting pagination behavior, which the schema's limit/offset hints at but the prose never mentions.

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?

Two sentences, no filler, and the most useful information (what the tool lists and its ordering) is front-loaded before the sibling disambiguation. Every clause carries information an agent needs.

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?

With only three simple scalar parameters, full schema coverage, and no output schema, the description supplies what is missing: the return payload's shape (event types plus time and build) and the ordering. Nothing needed to call this correctly is absent.

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 description coverage is 100%, so the baseline is 3; the description earns above that by clarifying that results are scoped to a single collector ('one collector's events') and that ordering is newest-first, which gives meaning to the limit/offset pagination that the schema only labels generically.

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 opens with a specific verb and resource ('List one collector's events') and then enumerates exactly what kinds of events come back: agent and sbproxy restarts, credential rotation, and unreachable-collector reports, each with time and build. It also explicitly contrasts itself with get_collector_health, so an agent can distinguish the two without reading either schema.

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?

It states both when to use it ('for a collector's recent history') and which alternative covers the other case ('get_collector_health gives its current state'). The selection condition between history and current state is spelled out rather than left to inference.

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