Skip to main content
Glama
legacy-switch-mcp

legacy-switch-mcp

backup_state

Save parsed switch state as a JSON file under ~/.local/state/switch-mcp/backups, with read-only access on the switch.

Instructions

Save the parsed state to a JSON file under ~/.local/state/switch-mcp/backups. Read-only on the switch.

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_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
switchYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description does real work by stating 'Read-only on the switch', which tells the agent this does not mutate device state, and by naming the target directory. It omits other behavioral facts a caller needs: how the filename is derived, whether an existing backup is overwritten, and what the tool returns.

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?

Two short sentences with no filler, and the primary action plus the storage location are front-loaded before the device-safety note.

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 simple single-parameter tool with no output schema and no annotations, the description covers the action, the destination path, and the non-mutating nature. It is still incomplete on parameter meaning and on what is returned or whether prior state parsing is required.

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 is never mentioned in the description. The agent must guess its expected format (name, host, or ID) from other tools, so the description fails to compensate for the schema gap.

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 concrete verb and resource: save the parsed state to a JSON file in ~/.local/state/switch-mcp/backups. The word 'parsed' distinguishes it from backup_config and backup_firmware, though it never names 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 through the name and the fact that it writes a local file rather than touching the device. There is no explicit guidance on when to pick this over get_state (read live state) or backup_config (save configuration), so the agent must infer the distinction.

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