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

io.github.ryanmat/logicmonitor

by ryanmat

get_remediationsource

Read-onlyIdempotent

Retrieve details for a LogicMonitor RemediationSource, including its Groovy script, by source ID; optionally return the full REST object for remediation setup.

Instructions

Get details about a specific RemediationSource including the Groovy script

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": {
      "source_id": "<source_id>"
    },
    "name": "get_remediationsource"
  }
}

Input Schema

NameRequiredDescriptionDefault
rawNoReturn the full REST object, the definition create_remediationsource takes, instead of the summary
source_idYesRemediationSource ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.0.1
    • addedInput schema / properties / raw
      Added value: +{
      +  "default": false,
      +  "description": "Return the full REST object, the definition create_remediationsource takes, instead of the summary",
      +  "type": "boolean"
      +}
  2. First observedv4.2.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already establish a read-only, idempotent, non-destructive open-world operation. The description adds the useful fact that Groovy script content is included, but provides no further behavioral context such as permissions, failure modes, or retrieval limitations.

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?

The single sentence is compact, front-loaded with the operation and resource, and ends with a useful payload detail. There is no filler or redundant restatement of schema fields.

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, the description, complete input schema, and safety annotations collectively supply enough information to invoke it correctly. The lack of an output schema is partly offset by the script mention and raw's output-shape documentation, though broader usage and error context remain absent.

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 the schema already explains both the integer source_id and raw's summary-versus-full-REST-object behavior, including its default. The description adds no parameter syntax or selection detail beyond that, so the high-coverage baseline applies.

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?

The description uses a clear verb and resource, "Get details about a specific RemediationSource," and narrows the result by mentioning the Groovy script. It conveys a single-source lookup, but does not explicitly differentiate the tool from siblings or related remediation workflows.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It implicitly suits an agent that already has a source ID and needs to inspect that source or its script. There is no explicit when-to-use, when-not-to-use, prerequisite-discovery, or alternative-tool guidance.

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