Skip to main content
Glama
legacy-switch-mcp

legacy-switch-mcp

list_switches

Lists configured switches with name, address, and vendor details; edit ~/.config/switch-mcp/switches.json to add more.

Instructions

Configured switches (name, address, vendor); edit ~/.config/switch-mcp/switches.json to add more.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_switches"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It usefully reveals the backing data source (~/.config/switch-mcp/switches.json) and the mutation path for adding entries, but omits whether the call is strictly read-only, what happens if the file is missing or empty, and whether ordering is guaranteed.

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?

A single compact sentence; the returned fields are front-loaded and the operational hint about the config file follows without wasted words. Nothing needs trimming or reordering.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter list tool with no output schema and no annotations, the description covers what an agent needs: what is listed, which fields, and where the data lives. Only edge-case behavior (missing config, ordering, empty result) is left unaddressed, which is a minor gap given the tool's simplicity.

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

Parameters4/5

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

The tool takes zero parameters, so per the baseline this scores 4. The description correctly implies there is nothing to supply and instead describes what comes back.

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 the resource (configured switches) and the fields returned (name, address, vendor), which is concrete enough for an agent to know this is a list operation. The word 'configured' implicitly distinguishes it from discovery-style siblings, though it does not name an alternative 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?

The guidance is implied rather than stated: 'configured' suggests a static inventory as opposed to runtime discovery, and the config-file path hints at when this is the right source. There is no explicit when-to-use, when-not, or named alternative tool for finding unconfigured devices.

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