Skip to main content
Glama
legacy-switch-mcp

legacy-switch-mcp

overview

Retrieves a consolidated view of a legacy switch in one login, including USRobotics main pages or D-Link parsed state.

Instructions

Everything useful in one login (USRobotics: its main pages; D-Link: the parsed state).

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>"
    },
    "name": "overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
switchYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.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 hints at vendor-specific output and a single-login scope, but does not disclose whether the operation is read-only, what authentication or session behavior it triggers, or what the response contains.

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?

The description is short and not padded, but it is not front-loaded with a clear statement of what the tool does. The parenthetical examples are useful, yet the opening phrase is cryptic rather than informative.

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?

For a tool with a required target parameter, no annotations, and no output schema, the description is far too thin. It does not explain how 'switch' is specified, what a caller receives, or how vendor differences affect results.

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

Parameters1/5

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

Schema description coverage is 0% and the description never mentions the required 'switch' parameter. An agent gets no meaning or format guidance for the only input beyond the bare schema property name.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives some concrete outcome details (USRobotics main pages, D-Link parsed state), but it never states a clear verb or resource such as 'return a consolidated overview of a switch.' The phrase 'Everything useful in one login' is vague and leaves the tool's actual purpose partly inferred from its name.

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 use this tool versus siblings like get_state, describe_switch, or list_interfaces. The phrase 'Everything useful' implies a broad overview, but no conditions, exclusions, or alternatives are mentioned.

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