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

io.github.ryanmat/logicmonitor

by ryanmat

get_apm_service_alerts

Read-onlyIdempotent

Retrieve paginated alerts for a specific APM trace service, with optional severity filtering, to inspect service health and troubleshoot issues.

Instructions

Get the alerts on one APM trace service, one page at a time

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": {
      "service_id": "<service_id>"
    },
    "name": "get_apm_service_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results
offsetNoResults to skip for pagination
severityNoFilter by alert severity
service_idYesAPM service device ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already establish readOnly, idempotent, non-destructive, and open-world behavior, lowering the description's burden. The description adds the pagination expectation ('one page at a time'), which is useful context beyond annotations, but it says nothing about ordering, rate limits, or response shape.

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?

The definition is a single, front-loaded sentence with no filler. It could be slightly more informative, but every word earns its place.

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?

For a read-only list tool with full schema coverage and complete safety annotations, the description is minimally sufficient. However, it omits the existence of severity filtering and gives no hint about what an alert record contains, which would help an agent know what to expect from the response.

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%, so the schema itself documents all four parameters including the severity enum and pagination defaults. The description only reinforces that service_id refers to a single APM trace service and that results are paged; it adds no syntax or behavioral meaning beyond the schema.

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 states a specific verb ('Get') and a precisely scoped resource ('the alerts on one APM trace service'), and adds the pagination scope ('one page at a time'). It is clear what the tool returns, but it does not explicitly distinguish itself from sibling alert tools such as get_alerts or get_alert_details.

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 when-to-use guidance, no when-not-to-use condition, and no mention of alternatives like get_alerts or analyze_alerts. The phrase 'one page at a time' describes pagination behavior rather than guiding tool selection.

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