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

io.github.ryanmat/logicmonitor

by ryanmat

get_collector_log_files

Read-onlyIdempotent

Lists the log files a collector has uploaded to LogicMonitor, with zip size and upload time, so you can confirm what was sent and then read one with get_collector_log_file.

Instructions

List the log files a collector has uploaded to the portal, as zip files with their size and upload time. A collector uploads them through Send Logs to LogicMonitor in the portal or the !uploadlog debug command, so an empty list means nothing was uploaded. Read one with get_collector_log_file.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "collector_id": "<collector_id>"
    },
    "name": "get_collector_log_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results
offsetNoPagination offset
collector_idYesCollector ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

A4.2/5.0
Behavior3/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 genuinely useful context beyond that: the return shape (zip files with size and upload time) and the meaning of an empty list. It does not discuss pagination behavior or rate limits, keeping it at a solid but not rich 3.

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 interpretation guidance, then the follow-up tool. No filler and nothing redundant with the schema.

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?

No output schema exists, and the description compensates by naming the returned fields (zip file, size, upload time). For a simple three-parameter read tool this is nearly complete; only pagination behavior is left implicit.

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?

Schema coverage is 100% and all three parameters are documented there, so the baseline is 3; the description goes slightly beyond by framing the result set as "log files a collector has uploaded," which implies how collector_id scopes the list. Still, it adds no detail on limit/offset semantics.

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 a specific verb and resource ("List the log files a collector has uploaded to the portal") and even distinguishes itself from the sibling that reads one file, so an agent can separate the list/read pair without opening either 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?

Explicitly routes content retrieval to get_collector_log_file and explains that an empty list means nothing was uploaded, which tells the agent how to interpret a result. It stops short of stating exclusions for the other log-related siblings (pipelines, partitions, usage), so it is clear 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