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

io.github.ryanmat/logicmonitor

by ryanmat

get_topologysource

Read-onlyIdempotent

Retrieve details for a specific LogicMonitor TopologySource using its ID, with an option to return the full REST object instead of the summary.

Instructions

Get details about a specific TopologySource

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": {
      "topologysource_id": "<topologysource_id>"
    },
    "name": "get_topologysource"
  }
}

Input Schema

NameRequiredDescriptionDefault
rawNoReturn the full REST object, the definition create_topologysource takes, instead of the summary
topologysource_idYesTopologySource 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_topologysource 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 without the description. The description contributes nothing beyond that: it does not say what happens when the ID is unknown, whether the response is a summary versus full object, or any permission requirement. The explanation of the 'raw' summary/full-object behavior lives only in the schema, not the description.

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?

It is a single short sentence with no wasted words, but the brevity reflects under-specification rather than disciplined front-loading. There is no structure to speak of because there is only one clause.

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-only lookup with a fully documented schema and complete annotations, this is minimally adequate — an agent can call it correctly. However, with no output schema, the description could have said what 'details' returns and noted that 'raw' selects the full object versus summary, which would have closed the remaining 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%, including an explanation of the 'raw' flag returning the full REST object instead of the summary, so the schema carries the parameter meaning. The description itself adds no syntax, format, or default information beyond the schema, making the baseline 3 appropriate.

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 uses a generic verb ('Get details about') applied to the resource named in the tool name itself, so it largely restates the name. It adds only the qualifier 'specific', which signals single-item retrieval by ID rather than listing, but gives no indication of what 'details' comprises or how it differs from any sibling.

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 statement about when not to use it, and no reference to any alternative such as a listing tool. The agent must infer from the parameter shape that an ID is required and that this is a single-record lookup.

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