Skip to main content
Glama
legacy-switch-mcp

legacy-switch-mcp

list_files

Lists saved configuration and firmware files with ID, size, and timestamp, newest first, without exposing file content.

Instructions

Saved configuration/firmware files (id, size, time; never content), newest first.

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

Input Schema

NameRequiredDescriptionDefault
switchNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, but it does disclose two genuinely useful traits: only metadata is returned ('never content') and results are ordered 'newest first'. It says nothing about pagination, completeness of the listing, or access requirements for a tool whose purpose is enumerating saved artifacts.

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?

One compact parenthetical sentence with zero filler, and the most decision-relevant facts (metadata only, newest first) are front-loaded. It is telegraphic rather than a full sentence, but nothing is wasted.

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?

Because an output schema exists, the field list need not be explained, and the tool is simple with one optional parameter. Still, missing usage routing and any explanation of the 'switch' filter leaves the definition only minimally sufficient for correct invocation.

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?

Schema description coverage is 0% and the single optional parameter 'switch' is never mentioned in the description, so an agent gets no explanation of what filtering by switch does or what omitting it returns. 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?

The description names the resource precisely (saved configuration/firmware files) and even enumerates the returned fields (id, size, time), which distinguishes it from siblings like list_snapshots or list_switches. There is no explicit statement of the verb or of which sibling to prefer, but the resource scope is unambiguous.

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?

No when-to-use guidance is given, and no alternative is named. An agent is not told whether this is the right tool for browsing backups versus reading a configuration, nor that content is unavailable and must come from another tool.

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