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

io.github.ryanmat/logicmonitor

by ryanmat

get_netscans

Read-onlyIdempotent

Lists network scans from LogicMonitor with pagination and optional name filtering to help you locate and review scan configurations.

Instructions

List network scans

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_netscans"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results
offsetNoPagination offset
name_filterNoFilter by netscan name (substring match)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv5.0.1
    • addedInput schema / properties / name_filter
      Added value: +{
      +  "description": "Filter by netscan name (substring match)",
      +  "type": "string"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "default": 0,
      +  "description": "Pagination offset",
      +  "type": "integer"
      +}
  2. 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, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not mention pagination behavior, default page size, filter semantics, or result ordering, all of which matter for a listing tool.

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 phrase is trivially concise and front-loaded, with zero wasted words. But it is concise to the point of under-specification for a tool with three parameters and pagination semantics.

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?

With annotations and a fully documented schema, the description does not need to explain return values or every parameter. Still, for a paginated list endpoint, it should at least signal that results are paginated and filterable by name, none of which it does.

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%, with limit, offset, and name_filter all documented in the schema, so the schema carries the parameter burden. The description adds no additional meaning, leaving this at the baseline.

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?

"List network scans" names a specific verb and resource, so an agent can tell it retrieves netscan records. However, it does nothing to differentiate this list endpoint from the many other get_* list endpoints among its siblings, beyond the resource noun itself.

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 mention of prerequisites, and no stated exclusions. An agent must infer everything from the title-level phrase.

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