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

io.github.ryanmat/logicmonitor

by ryanmat

get_topology_map

Read-onlyIdempotent

Retrieve network topology map data with pagination and optional connection details to visualize device relationships.

Instructions

Get network topology map data

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_topology_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results
offsetNoPagination offset
include_connectionsNoInclude connection data

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.0.1
    • addedInput schema / properties / offset
      Added value: +{
      +  "default": 0,
      +  "description": "Pagination offset",
      +  "type": "integer"
      +}
  2. Changed1 schema field changedv4.3.0
    • removedInput schema / properties / device_group_id
      Removed value: -{
      -  "description": "Filter by device group ID",
      -  "type": "integer"
      -}
  3. First observedv4.2.0

TDQS

C2.5/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 covered without the description. The description adds nothing beyond that — no information about the size or shape of a topology map, how expensive the call may be, or what openWorld access implies for results. It repeats rather than extends the structured data.

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?

A single short sentence with no wasted words and the resource front-loaded. However, brevity here comes at the cost of substance — the sentence earns its place only minimally because it conveys nothing the tool name does not already convey.

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

Completeness2/5

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

There is no output schema, so the description should explain what a topology map contains and how pagination interacts with a graph-shaped result. It says nothing about return content, scope, or size, leaving the agent unable to anticipate the response for a tool whose annotations signal open-world access.

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 limit, offset, and include_connections are already documented in the schema, establishing a baseline of 3. The description does not mention pagination or the connections toggle at all, so it contributes no additional parameter meaning.

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 states a verb and resource ("Get network topology map data"), so the agent knows it retrieves topology data. But "topology map data" is left undefined — no mention of nodes, links, devices, or which network scope — so the agent cannot tell what the returned map actually represents. It is adequate but vague rather than a clear, specific statement of purpose.

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, no prerequisites, and no exclusions. The only implied context is 'you want topology data', which the agent must infer entirely from the name.

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