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

io.github.ryanmat/logicmonitor

by ryanmat

get_collector_log_file

Read-onlyIdempotent

Read one uploaded LogicMonitor collector log file and return the end of its text, limited by max_bytes and starting on a whole line, with a flag showing whether earlier lines were truncated.

Instructions

Read one uploaded collector log file, named as get_collector_log_files lists it, and return the end of its text: at most max_bytes bytes, starting on a whole line. truncated says whether earlier lines were left out.

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>",
      "file_name": "<file_name>"
    },
    "name": "get_collector_log_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_nameYesLog file name, such as 82.postcheck.log.zip
max_bytesNoMost bytes of the log's end to return
collector_idYesCollector ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so safety is covered. The description adds real behavior beyond that: it returns only the END of the file, caps at max_bytes, begins on a whole line, and exposes a truncated indicator for earlier omitted lines — critical context an agent would otherwise have to infer from a partial view.

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 well-formed sentence with the salient scope front-loaded (one file, named via the listing tool) followed by the return contract. No filler, and the trailing clause usefully defines the truncated indicator.

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?

With no output schema, the description carries the return-value explanation and does it well for a three-parameter read tool. It leaves minor unknowns — behavior when the file is absent, and that the example name has a .zip suffix while the description speaks of text — but nothing an agent needs in order to invoke it correctly.

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%, so max_bytes and file_name are already documented, giving a baseline of 3. The description earns above baseline by explaining what max_bytes actually bounds (bytes of the log's end) and that truncation results in whole-line boundaries and a truncated flag, which the schema does not state.

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 (read one uploaded collector log file) plus the exact return semantics (the tail of the text, capped at max_bytes, starting on a whole line). It also distinguishes itself from the listing sibling by pointing at get_collector_log_files as the source of the file name.

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?

Clear context for use: the file must be one that get_collector_log_files lists, which routes the agent to the sibling first rather than guessing names. There is no explicit when-not guidance or discussion of error conditions (missing file, non-log file), so it stops short of a 5.

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