Skip to main content
Glama
Systems Manager

Systems Manager

List Open Ports

sm_network_list_open_ports
Read-onlyIdempotent

Lists open ports on a system for network analysis, helping identify exposed services and assess connectivity or security posture.

Instructions

List open ports (sm_network_operations). Operations for network analysis

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": "sm_network_list_open_ports"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.11

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 covered. The description adds nothing beyond that: it does not say whether the ports listed are local listening sockets or a remote scan, nor whether results are sorted, cached, or filtered. The openWorldHint=true annotation makes the local-vs-remote ambiguity a meaningful omission.

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 core statement is front-loaded and short, which is good. However, the parenthetical tool-family tag and the generic filler "Operations for network analysis" occupy roughly half the text without earning their place, diluting an already thin description.

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?

For a zero-parameter read-only list tool the bar is low, but the single genuinely important question - what an "open port" means here and what scope is inspected - goes unanswered, and there is no output schema to fall back on. An agent cannot predict the shape or domain of the results from this definition.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. No misleading parameter information is present.

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?

"List open ports" gives a specific verb plus resource that an agent can act on directly. The trailing parenthetical "(sm_network_operations)" and "Operations for network analysis" add no differentiating information, so it does not distinguish itself from siblings such as get_network_connections that may also expose port information.

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 statement of when to use this versus alternatives, and no prerequisites or exclusions. With sibling tools like get_network_connections and sm_network_list_network_interfaces in the catalog, the agent is left to guess which surface answers a port question.

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