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

io.github.ryanmat/logicmonitor

by ryanmat

get_diagnosticsource

Read-onlyIdempotent

Retrieve details for a specific LogicMonitor DiagnosticSource by ID, including its datapoints. Use it to inspect source configuration or fetch the full REST object when raw output is needed.

Instructions

Get details about a specific DiagnosticSource including datapoints

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

Input Schema

NameRequiredDescriptionDefault
rawNoReturn the full REST object, the definition create_diagnosticsource takes, instead of the summary
source_idYesDiagnosticSource 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_diagnosticsource takes, instead of the summary",
      +  "type": "boolean"
      +}
  2. First observedv4.2.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered. The description adds only that the payload includes datapoints; it says nothing about result size, pagination, or behavior on a missing ID, which is a modest gap for a read tool.

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

Conciseness4/5

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

A single front-loaded sentence with no filler. It is efficient, though arguably under-specified rather than truly concise.

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 tool with fully documented schema, rich annotations, and no output schema, the definition covers what the tool returns and what it needs. Only the lack of alternative-routing guidance keeps it from a 5.

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%, including an explanation of the raw flag that the description does not repeat. Baseline 3 applies; the description adds no parameter meaning beyond the schema.

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 (get a DiagnosticSource by id) and adds that datapoints are included in the result, which is meaningful scope information. It does not explicitly distinguish itself from the plural list variant or from get_configsource, but the singular-by-id purpose is unambiguous.

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 guidance on when to use this versus a listing tool or a sibling getter, and no prerequisites or exclusions. The required source_id implies a known ID, but the agent must infer that from the schema rather than the description.

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