Skip to main content
Glama
legacy-switch-mcp

legacy-switch-mcp

get_state

Retrieve read-only parsed switch state, including VLANs, groups, ports, mirror, trunks, and system, to inspect configuration before changes.

Instructions

Parsed state: VLANs/groups, ports, mirror, trunks, system. 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": "get_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
switchYes

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?

Annotations are absent, so the description carries the full burden, and it does affirmatively disclose the most important trait: this does not mutate the device. However, it says nothing about whether the state is live-query or cached, connection/permission requirements, latency, or failure behavior on an unreachable switch.

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 fragments with zero filler; the payload contents and the read-only property are both front-loaded. The telegraphed style ('system') is slightly cryptic but not wasteful.

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?

With no output schema, listing the parsed sections usefully signals the return shape, which is the description's strongest contribution. It is still incomplete for a tool whose sole parameter is undocumented and whose execution semantics (live vs cached) are unstated.

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?

One required parameter ('switch') with 0% schema description coverage, and the description never mentions it — no indication of identifier format (name, IP, serial, alias) or whether it must match a value from list_switches. With coverage below 50%, the description needed to compensate and does not.

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?

Names the resource concretely and enumerates the parsed sections returned (VLANs/groups, ports, mirror, trunks, system), so an agent knows this is a composite switch-state read rather than a single-facet list. No verb and no explicit contrast with overlapping siblings such as list_interfaces or describe_switch, which keeps it from a 5.

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?

The only usage signal is the trailing 'Read-only.' There is no statement of when to prefer this over describe_switch, list_interfaces, or overview, no prerequisites, and no exclusions.

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