Skip to main content
Glama
legacy-switch-mcp

legacy-switch-mcp

discover

Sends broadcast and multicast requests on a specified interface to identify reachable devices without changing any configuration.

Instructions

Broadcast/multicast discovery on one interface (e.g. vmbr0). Sends requests only; changes nothing.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "interface": "<interface>"
    },
    "name": "discover"
  }
}

Input Schema

NameRequiredDescriptionDefault
interfaceYes
wait_secondsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does add real value by declaring 'Sends requests only; changes nothing', which tells the agent the operation is non-mutating. However it omits what the agent most needs to know: whether the call blocks for the wait window, that broadcast traffic is emitted onto the named interface, and any privilege requirements.

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?

Two short sentences, front-loaded with the operation and resource, with the safety note second. Nothing is wasted, though the extreme terseness is part of why behavioral and parameter detail are missing.

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 presence of an output schema relieves the description of explaining return values, and the non-mutating claim covers the safety question. Still, for a network-emitting tool with an undocumented timing parameter, the definition leaves out how long it runs and what side effects the broadcast has on the interface.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for two undocumented parameters. It partially does so for 'interface' by giving the vmbr0 example, but says nothing about 'wait_seconds' (default 3), leaving unclear whether it is a listen duration, a timeout, or a poll interval. Half the parameters remain semantically opaque.

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?

States a specific action (broadcast/multicast discovery) against a specific resource (one interface) and anchors it with a concrete example value, vmbr0. It does not distinguish itself from potentially overlapping siblings such as probe or list_interfaces, so it stops 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 Guidelines3/5

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

The phrase 'discovery on one interface' implies the scenario, but there is no explicit when-to-use, no when-not-to-use, and no pointer to probe or list_interfaces as alternatives for related discovery needs. Guidance is inferable rather than stated.

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