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

io.github.ryanmat/logicmonitor

by ryanmat

get_apm_services

Read-onlyIdempotent

List and filter APM trace services page by page to discover traced services; use returned service IDs to read datasources, operations, metrics, and properties.

Instructions

List APM trace services, the deviceType 6 devices, one page at a time. Entry point for discovering traced services; read a service's datasources, operations (the instances of its operations datasource), metrics and properties with get_device_datasources, get_device_instances, get_device_data and get_device_properties, passing the service id as device_id.

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_apm_services"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results
offsetNoResults to skip for pagination
name_filterNoFilter by service display name (substring match)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, and the description adds pagination behavior ('one page at a time'), the deviceType 6 scope, and the downstream query path. It does not cover auth, rate limits, or return shape, but with annotations carrying the safety profile this is useful extra context.

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, front-loaded with the purpose and pagination constraint, followed by a compact routing sentence. The downstream-tool list is dense but every element is functional, with no filler.

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?

For a read-only discovery list with three optional, fully documented params and no output schema, the definition supplies purpose, pagination scope, and the exact next tools to call. Nothing essential for correct invocation is missing.

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 limit, offset, and name_filter fully described, so the schema carries parameter meaning. The description only reinforces pagination and does not add syntax or filtering semantics beyond the schema; baseline 3 is appropriate.

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?

States 'List APM trace services' and scopes it to 'deviceType 6 devices,' which distinguishes this from generic service listings. It also frames the tool as the entry point for traced-service discovery, so an agent can identify the resource and intent without opening the 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?

Explicitly says this is the entry point for discovering traced services and directs follow-up reads to get_device_datasources, get_device_instances, get_device_data, and get_device_properties, including passing the service id as device_id. It does not spell out a negative case, but the discovery-vs-detail split is clear.

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