Skip to main content
Glama
legacy-switch-mcp

legacy-switch-mcp

list_interfaces

Lists IPv4 interfaces on the host that discovery can use, helping you identify available network addresses before inspecting or configuring legacy smart switches.

Instructions

IPv4 interfaces on this host that discovery can use.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose a real behavioral constraint: only interfaces usable by discovery are returned. However, it says nothing about whether non-IPv4 or down interfaces are omitted, whether the list is host-local only versus enumerated remotely, or any side effects of the call.

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?

It is a single short clause with no wasted words, and the scoping qualifier is placed immediately after the resource. The fragmentary phrasing (no subject or verb) makes it slightly less self-contained than an ideal front-loaded sentence.

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

Completeness3/5

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

The tool is simple (no parameters, output schema present, so return values need not be explained), and the description identifies the resource and scope. It still leaves open the practical question of what qualifies as 'usable by discovery' and whether the caller should run discover afterward, which matters for correct sequencing.

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 meaning for the description to supply. The baseline of 4 applies; the description correctly avoids inventing filtering options that do not exist in the schema.

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 description names a specific resource (IPv4 interfaces) and scopes it to those 'discovery can use' on 'this host', which distinguishes it from a generic file/snapshot/switch listing. It lacks an explicit verb ('list'), relying on the tool name for the action, so it falls just short of a 5.

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 explicit guidance on when to call this versus alternatives such as discover or list_switches. The phrase 'that discovery can use' hints at a relationship to the discover tool, but the agent must infer the ordering and any exclusions on its own.

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