Skip to main content
Glama
legacy-switch-mcp

legacy-switch-mcp

read_page

Retrieves a single raw web UI page from a USRobotics or D-Link switch for read-only inspection of status, VLAN, port, trunk, mirror, or system settings.

Instructions

One raw page of a switch's web UI. USRobotics: status, port, vlan, trunk, mirror, statistics, system, trap. D-Link: system, vlan, port, mirror, pvlan, mgmt_vlan, trunk. Read-only.

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": {
      "switch": "<switch>",
      "page": "<page>"
    },
    "name": "read_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYes
switchYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose two useful traits — the output is a single 'raw' page (agent must parse it) and the operation is 'Read-only' — but says nothing about authentication to the switch web UI, error behavior for invalid page names, case sensitivity, or what exactly 'raw' contains.

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?

Purpose is front-loaded in the first sentence, followed by compact vendor/page lists and a one-word safety note — no filler. The vendor page lists are run together as bare comma sequences, which is dense but still readable.

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?

With no annotations, no output schema, and 0% schema coverage on a required 2-parameter tool, the description leaves real gaps: the meaning of `switch`, the format of the 'raw' return value, and failure modes for unknown pages. The page enumeration offsets some of that, making it adequate but not complete.

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%, so the description must compensate for both parameters. It effectively supplies the missing enum for `page` by listing valid page names per vendor family, which is genuinely valuable. However, the `switch` parameter is never explained (identifier, IP, or list index?), and there is no indication of how a caller knows which vendor list applies.

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 concrete resource and scope: 'One raw page of a switch's web UI,' with 'raw' signalling unparsed output rather than the structured data that siblings like get_state or overview likely return. It does not explicitly name a sibling or state the boundary against them, 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?

Usage is implied rather than stated: by enumerating per-vendor page names (USRobotics vs. D-Link), the description hints this is the escape hatch for vendor-specific pages. It never says when to prefer read_page over the structured sibling tools, or what to do when a page name is unsupported for a given vendor.

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