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

io.github.ryanmat/logicmonitor

by ryanmat

get_batchjobs

Read-onlyIdempotent

Retrieve and filter LogicMonitor batch jobs by status or name, with pagination controls to locate specific jobs and manage results.

Instructions

List batch jobs

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results
offsetNoPagination offset
statusNoOnly jobs with this status (active, inactive)
name_filterNoFilter by job name (substring match)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv5.0.1
    • addedInput schema / properties / name_filter
      Added value: +{
      +  "description": "Filter by job name (substring match)",
      +  "type": "string"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "default": 0,
      +  "description": "Pagination offset",
      +  "type": "integer"
      +}
    • addedInput schema / properties / status
      Added value: +{
      +  "description": "Only jobs with this status (active, inactive)",
      +  "type": "string"
      +}
  2. First observedv4.2.0

TDQS

C2.7/5.0
Behavior2/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 covered. The description adds nothing beyond that: no note on whether results are paginated totals, whether the list is account-wide, or how an empty result should be interpreted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The fragment is trivially free of waste and front-loaded, but its brevity comes at the cost of any substance. It reads as an unfinished label rather than a structured description.

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?

Considering complexity: four optional parameters fully documented in the schema, rich annotations, and no output schema, so the structured data carries most of the load. The description is thin but the residual risk of misuse is limited; a note distinguishing it from get_batchjob and get_device_batchjobs would have completed it.

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 all four parameters (limit, offset, status, name_filter) individually documented, so the baseline of 3 applies. The description contributes no additional meaning about parameter interaction, such as whether status accepts multiple values or how name_filter matching behaves.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description supplies a verb ("List") and a resource ("batch jobs"), so the basic operation is identifiable. However, it is essentially a restatement of the tool name get_batchjobs and gives no scope or filtering context, leaving the agent unable to distinguish it from siblings like get_batchjob (singular detail) or get_device_batchjobs.

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 guidance, no stated prerequisites, and no mention of alternatives such as get_batchjob for single-record retrieval. The agent must infer selection from names alone.

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