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

io.github.ryanmat/logicmonitor

by ryanmat

get_service_insights_rules

Read-onlyIdempotent

List a LogicMonitor portal's Service Insights rules as API rows with paginated limit and offset; offset must be a multiple of limit, and use get_services for services.

Instructions

List the portal's Service Insights rules, rows as the API returns them. offset must be a multiple of limit; the portal answers any other offset with a 400. get_services lists the services themselves.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_service_insights_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results
offsetNoPagination offset, a multiple of limit

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

A3.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 adds genuinely new behavior beyond that: an invalid offset produces a 400 from the portal, and rows are returned as the API emits them with no transformation. It does not discuss pagination termination or result volume, which is a minor gap.

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?

Three short, front-loaded sentences with no filler; the core identification comes first and the constraint follows. "rows as the API returns them" is slightly imprecise, but it does communicate that no reshaping occurs.

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

Completeness4/5

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

For a two-parameter, read-only list tool with full schema coverage and annotations covering the safety profile, this is close to sufficient. Since there is no output schema, the note about unmodified rows helps, though the shape of a rule row is never hinted at.

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% and the schema already labels offset as "a multiple of limit", so the description is largely restating structured data. The one added piece of meaning is the concrete consequence of violating the constraint (a 400 response), which makes it slightly more than baseline but not rich.

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 gives a specific verb and resource ("List the portal's Service Insights rules") and adds that results are returned unmodified ("rows as the API returns them"). It also differentiates from get_services by noting that tool lists services themselves, though the closer siblings get_action_rules and get_alert_rules are not addressed.

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

Usage Guidelines3/5

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

Usage context is implied by the resource name and one alternative (get_services) is named, but there is no explicit statement of when to choose this over the other rule-listing siblings. The offset constraint is a calling precondition rather than selection guidance.

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