Skip to main content
Glama
monitoringartist

LogicMonitor MCP Server

by monitoringartist
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

get_netscan

Read-only

Retrieve complete configuration details of a LogicMonitor netscan, including targets, schedule, credentials, filters, and duplicate detection settings, to troubleshoot resource discovery issues.

Instructions

Get detailed information about a specific netscan by ID in LogicMonitor (LM) monitoring.

Returns: Complete netscan details: name, description, scan method, schedule, target networks/IPs, credentials, filters (include/exclude rules), resource/device properties to apply, collector assignment, duplicate detection settings, last execution results.

When to use:

  • Review netscan configuration before running

  • Troubleshoot why certain resource/device not discovered

  • Check credentials and filters

  • Verify resource/device properties applied to discovered resources/devices

  • Understand duplicate detection logic

Configuration details returned:

  • Targets: IP ranges, subnets, or cloud filters (e.g., "192.168.1.0/24", "All EC2 with tag:Environment=prod")

  • Schedule: How often scan runs (hourly, daily, weekly, on-demand)

  • Credentials: Which properties used for authentication (ssh.user, snmp.community)

  • Filters: Include/exclude rules (e.g., "Exclude IPs ending in .1", "Only Linux servers")

  • Device properties: Auto-applied to discovered resource/device (e.g., location, environment tags)

  • Duplicate handling: How to handle resource/device found in multiple scans

Troubleshooting use cases:

  • "Why resource/device not discovered?" → Check if IP in target range and not excluded by filters

  • "Wrong credentials?" → Verify credential properties configured in netscan

  • "resources/Devices missing properties?" → Check default properties applied by netscan

Workflow: Use "list_netscans" to find netscanId, then use this tool to review complete configuration.

Related tools: "list_netscans" (find netscan), "update_netscan" (modify), "run_netscan" (execute now).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
netscanIdYesThe ID of the netscan to retrieve
fieldsNoComma-separated list of fields to include in response. Examples: "id,displayName,hostStatus" or use "*" for all fields. Omit this parameter to receive a curated set of commonly used fields.

Tool Definition Quality

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true. The description adds detailed behavioral context by listing what configuration details are returned and troubleshooting use cases, without contradicting annotations.

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 well-structured with headers and bullet points, and the core purpose is front-loaded. While somewhat verbose, every section adds value for an AI agent.

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

Completeness5/5

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

Given no output schema, the description thoroughly lists the returned configuration details and troubleshooting use cases. It covers all expected behavior for a read-only retrieval tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds extra context by explaining the netscanId as obtained from list_netscans and implicitly describes the fields parameter through the troubleshooting examples. This raises the score above baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Get detailed information about a specific netscan by ID' with a specific verb and resource. It also distinguishes from siblings by mentioning list_netscans, update_netscan, and run_netscan as related tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'When to use' section lists specific scenarios like reviewing configuration before running and troubleshooting discovery. It also provides a workflow linking to list_netscans and distinguishes from update/run tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/monitoringartist/logicmonitor-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server