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

io.github.ryanmat/logicmonitor

by ryanmat

get_log_pipelines

Read-onlyIdempotent

Lists all LogicMonitor LM Logs pipelines with each pipeline's log query and named partitions, returning every pipeline in one call without searching log content.

Instructions

List every LM Logs pipeline with its log query and the partitions it names. It returns all pipelines at once and takes no arguments. It does not search log content.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 read-only, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description still adds meaningful behavior beyond them: results are returned for all pipelines in a single call with no arguments, implying no pagination or filtering, and it clarifies the scope boundary against log-content search.

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?

Three short sentences, front-loaded with what is returned, then call shape, then scope exclusion. Every sentence carries distinct information with no filler or restatement of the title.

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 zero-argument list tool with no output schema, the description covers what comes back (pipelines with their log queries and named partitions), that all results arrive at once, and what the tool does not do. Nothing an agent needs to invoke it correctly is missing.

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?

With zero parameters the baseline is 4, and the description correctly confirms "takes no arguments," matching the empty schema. Nothing further is needed or possible on this dimension.

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?

Names a specific verb and resource ("List every LM Logs pipeline") and immediately characterizes the payload: each pipeline's log query and the partitions it names. The closing sentence ("does not search log content") separates it from log-search tools, so an agent can distinguish it from siblings like get_log_partitions or get_log_query_groups 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 Guidelines4/5

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

Gives clear positive context (enumerate all pipelines) and an explicit exclusion ("does not search log content"), which steers an agent away from using it as a log search entry point. It stops short of naming a specific alternative tool to use instead, so the routing guidance is strong but not exhaustive.

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