Skip to main content
Glama
legacy-switch-mcp

legacy-switch-mcp

backup_config

Downloads a legacy switch configuration file to the state directory for local retention, returning its ID, size, and checksum.

Instructions

Download the configuration file to the state directory (mode 0600; it is a secret). Returns only id, size, checksum. 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>"
    },
    "name": "backup_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
switchYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the filesystem side effect (writing into the state directory), the restrictive mode 0600, that the content is a secret, that the operation is read-only, and that the response is truncated to id/size/checksum. Gaps remain on overwrite behavior, rate limits, and whether the file is re-downloaded or cached.

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?

Three short clauses, purpose front-loaded, then permissions/secret warning, then return shape. Nothing is padded and every sentence adds information the schema does not carry.

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 tool with no output schema and no annotations, it usefully covers return values, file permissions, and read-only semantics. The undefined 'switch' argument is the notable remaining hole an agent needs to call it correctly.

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' has 0% schema description coverage and the description never explains it — whether it is a name, index, IP, or object handle, or how to obtain a valid value. With only one parameter, this omission is the main semantic deficit.

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 and resource: 'Download the configuration file to the state directory'. That is clearly distinguishable from backup_firmware and backup_state by the object acted on. It stops short of naming or contrasting those siblings explicitly.

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 only implied by the action and the '(it is a secret)' note; there is no statement of when to prefer this over backup_state or backup_firmware, and no preconditions such as required connectivity or prior snapshotting.

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