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

io.github.ryanmat/logicmonitor

by ryanmat

get_logsource

Read-onlyIdempotent

Retrieves detailed information for a specific LogicMonitor LogSource by ID, returning either a summary or the full REST object definition used by create_logsource.

Instructions

Get details about a specific LogSource

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": {
      "logsource_id": "<logsource_id>"
    },
    "name": "get_logsource"
  }
}

Input Schema

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

TDQS

C2.6/5.0
Behavior2/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 structurally. The description adds nothing beyond that — no note about what happens with unknown IDs, no cost/latency context, and no mention of the summary-vs-raw return behavior that the schema param implies.

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 single sentence is front-loaded and free of padding, so there is nothing to trim. However, its brevity reflects under-specification rather than efficiency: no sentence conveys information the agent did not already have from the name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a low-complexity two-parameter read tool with rich annotations and a fully documented schema, so the minimal description is close to sufficient. The main gap is that no output schema exists and the description says nothing about what 'details' comprise or how the default summary differs from the raw object.

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%, so both parameters (logsource_id and the raw flag) are already documented in the schema, and the baseline is 3. The description adds no additional meaning about parameter effects, such as when raw output is worth requesting.

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 sentence 'Get details about a specific LogSource' pairs a verb with a resource, but it essentially restates the tool name (get_logsource) and the title-less naming already implies retrieval. It does hint at single-object retrieval ('a specific') versus a list, yet it never names or contrasts the sibling list tool, so differentiation is left to inference.

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: nothing says to call this when you have a resolved logsource_id rather than listing logsources first, and no exclusions or alternatives are mentioned. The agent must infer usage purely from the tool name and required ID parameter.

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