Skip to main content
Glama
Systems Manager

Systems Manager

List Network Interfaces

sm_network_list_network_interfaces
Read-onlyIdempotent

List network interfaces on managed hosts to support network analysis and troubleshooting.

Instructions

List network interfaces (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_network_interfaces"
  }
}

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, idempotentHint, openWorldHint and destructiveHint=false, so safety is fully covered. The description adds nothing beyond that — no note on output shape, scope (local host only vs remote), or ordering — so it contributes no behavioral context the agent doesn't already have.

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 short, which is appropriate, but the second fragment 'Operations for network analysis' is vague filler that does not earn its place. The useful content is a single four-word clause.

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?

This is a simple zero-argument read tool with rich annotations, so little is required. However, with no output schema the description should at least hint at what an interface entry contains (name, addresses, state) and whether results cover all local interfaces; it says none of that.

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 no parameter semantics to explain and the baseline of 4 applies. Nothing in the description is needed or misleading here.

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?

The first clause states a specific verb and resource: list network interfaces. It does not, however, contrast itself with close siblings such as sm_network_list_open_ports or get_network_connections. The trailing parenthetical 'sm_network_operations' is just a namespace label and adds no discriminating 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 guidance on when to choose this over the many sibling 'list' tools or the network-specific alternatives. 'Operations for network analysis' is a category label, not a condition for use, and no exclusions or prerequisites are given.

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