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

io.github.ryanmat/logicmonitor

by ryanmat

get_log_query_groups

Read-onlyIdempotent

List saved LogicMonitor Logs query groups (folders) with their type, owner, permissions, and contained queries; use it to inspect and navigate stored log query organization.

Instructions

List the saved LM Logs query groups (folders) with their type, owner, permission and the queries each holds.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results
offsetNoPagination offset

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

B3.4/5.0
Behavior3/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 fully carried by structured data. The description adds the returned content (type, owner, permission, contained queries), which is genuine value, but says nothing about ordering, empty-result behavior, or whether permissions restrict visibility.

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?

A single front-loaded sentence that names the action, the resource, and its contents with no redundant or filler wording.

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 simple two-parameter read with rich annotations and no output schema, the description usefully enumerates the returned fields, compensating for the missing output schema. Only minor gaps remain (result ordering and permission-scoped visibility), which are unlikely to block a correct call.

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% and both parameters (limit, offset) carry defaults and descriptions, so pagination semantics are fully documented structurally. The description adds nothing beyond the schema, which is the expected baseline-3 case.

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?

States a specific verb (List) and resource (saved LM Logs query groups/folders), and clarifies the entity by glossing it as 'folders' plus enumerating the returned fields. An agent can distinguish it from pipeline/tracked-query siblings by the 'groups (folders)' framing, though no sibling is named explicitly.

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, when-not-to-use, or alternative routing guidance. The nearest ambiguous sibling, get_tracked_log_queries, is never mentioned, so the agent must infer from the word 'groups' that this is a container-listing call rather than a query listing.

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