Skip to main content
Glama
legacy-switch-mcp

legacy-switch-mcp

backup_firmware

Download a D-Link switch's running firmware image to the state directory for read-only backup; USRobotics models have no firmware image to save.

Instructions

Download the D-Link's running firmware image (~740 KB) to the state directory. Read-only; the USRobotics has none.

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

Input Schema

NameRequiredDescriptionDefault
switchYes

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?

With no annotations supplied, the description carries the full burden and does disclose useful traits: read-only nature, approximate payload size, write destination, and a device limitation. It omits what happens on overwrite, error modes, and any authentication/host requirements, leaving meaningful gaps for a file-writing operation.

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 action and resource. Minor awkwardness in "the D-Link's" phrasing costs nothing material.

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?

For a one-parameter tool with no output schema, the description covers destination, size, safety profile, and a device constraint. The unresolved meaning of the required "switch" argument is the main completeness gap.

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?

The single required parameter "switch" is undocumented in the schema (0% coverage) and the description never explains its expected form (hostname, IP, model, or index). The D-Link/USRobotics remarks hint that device identity matters but do not define the value to supply.

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 verb (download) and resource (running firmware image), plus a destination (state directory) and size (~740 KB), which distinguishes it from backup_config by resource type. It does not explicitly name the sibling it differs from, so an agent must infer firmware-vs-config separation from the noun.

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?

"Read-only; the USRobotics has none" gives one exclusion condition, implicitly warning not to call this on USRobotics hardware. There is no explicit statement of when to prefer this over backup_config or backup_state, so the routing decision is only implied.

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