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

io.github.ryanmat/logicmonitor

by ryanmat

get_datasource

Read-onlyIdempotent

Retrieve details for a specific LogicMonitor datasource by ID, returning either a summary or the full REST definition for auditing, editing, or creating matching datasources.

Instructions

Get details about a specific datasource

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": {
      "datasource_id": "<datasource_id>"
    },
    "name": "get_datasource"
  }
}

Input Schema

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

TDQS

C2.9/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 no behavioral context beyond that—nothing about permissions, error behavior for invalid IDs, or what 'details' includes—so it contributes essentially nothing beyond the name.

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?

The description is a single short sentence with no filler, and the essential action is front-loaded. It is efficient, though its brevity contributes to the missing guidance noted elsewhere.

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?

For a simple two-parameter read tool, the description is minimally adequate, especially since the schema fully documents parameters and annotations cover safety. However, with no output schema present, the description does not indicate what 'details' returns or when the raw form should be requested, leaving a small gap.

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, including the meaningful 'raw' flag that switches between the full REST object and the summary, are already documented in the schema. The description adds no additional meaning, which meets the baseline of 3 when the schema carries the full burden.

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 names a specific verb and resource ('Get details about a specific datasource'), which is clear enough for an agent to understand the operation. It does not explicitly contrast with the nearby sibling get_datasource_devices, but the narrower scope (one datasource vs. its devices) is implied by 'details about a specific datasource'.

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 tool versus alternatives such as get_configsource or get_datasource_devices, and no stated prerequisites. The description only implies usage through the singular datasource target, leaving the agent to infer context from the sibling names.

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