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

io.github.ryanmat/logicmonitor

by ryanmat

get_tracked_log_queries

Read-onlyIdempotent

List the portal's tracked log queries to see which queries are tracked; this does not execute or run them.

Instructions

List the portal's tracked log queries, each row as the API returns it. Use it to see which log queries the portal tracks; it does not run them.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results
offsetNoPagination offset

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds two things beyond them: the non-execution guarantee (no side effects on the queries themselves) and 'each row as the API returns it', which tells the agent the return values are a raw passthrough shape — useful context given there is no output schema. Pagination behavior is left to the schema.

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 short sentences, front-loaded with the resource and followed by the use case plus the negative constraint. No filler or restated boilerplate; every clause carries information.

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 read-only list endpoint with two optional pagination params, full annotation coverage and no output schema, this is close to sufficient: purpose, non-execution, and raw-row return shape are all stated. Only the absence of any hint about what fields a row contains leaves a small gap.

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% with only limit and offset, both already documented inline, and the description adds no further semantics about them. Baseline 3 is appropriate since the schema does all the work here.

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 and resource: 'List the portal's tracked log queries', and adds a disambiguating clause that it does not run them, which separates it from anything query-execution related among the siblings. It does not explicitly distinguish itself from adjacent resources such as log query groups or log pipelines, so an agent still has to rely on the resource name alone there.

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?

'Use it to see which log queries the portal tracks' gives a clear positive use case, and 'it does not run them' supplies an explicit exclusion. What is missing is a named alternative for the case the agent actually wants to execute or inspect query results.

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