Skip to main content
Glama
legacy-switch-mcp

legacy-switch-mcp

probe

Queries a single legacy switch by IP address across subnets and returns its discovery reply, or an error when it is unreachable.

Instructions

Ask one switch by IP (works across subnets); returns its discovery reply or {"error": ...}.

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": {
      "host": "<host>"
    },
    "name": "probe"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 disclosure burden. It does valuable work by stating the return contract — a discovery reply, or an `{"error": ...}` object — which tells the agent failures are reported in-band rather than thrown. It says nothing about timeouts, credentials, or network side effects of contacting a device, which matters for a tool that talks to hardware.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence, front-loaded with the action and target, with the cross-subnet caveat and return shape tucked into compact clauses. Nothing is padded and nothing repeats the tool name.

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

Completeness4/5

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

For a one-parameter probe with no output schema, the description covers the essential unknowns: single target, IP-addressed, cross-subnet capable, and the shape of both success and error results. The remaining gap — no mention of timeout or auth expectations when reaching a device — is minor for a read-style probe.

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 coverage is 0%: the single `host` parameter is documented only as a bare string. The description partially compensates by indicating the value is an IP address ("by IP"), which rules out hostnames, but gives no format or address-family detail beyond that.

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?

"Ask one switch by IP" gives a concrete verb-ish action, a specific resource (one switch), and a scoping qualifier ("one", "by IP") that distinguishes it from a fleet-wide scan. It stops short of naming the sibling `discover`, so an agent must infer that this is the single-host variant, but the intent is still readable without the schema.

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 parenthetical "works across subnets" implies when this is the right call (a target not reachable by local broadcast discovery), which is a genuine usage signal. There is no explicit when-not or named alternative such as `discover` or `describe_switch`, so the agent must infer the boundary.

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