Skip to main content
Glama
Sign In
Device MCP Server

Device MCP Server

by rajib884
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

connect_device

Establish a persistent SSH or Telnet connection to network devices for command execution. Supports authentication and multiple platform drivers.

Instructions

Connect to a network device via SSH or Telnet.

Establishes a persistent connection for command execution.

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": {
      "host": "<host>",
      "username": "<username>",
      "password": "<password>"
    },
    "name": "connect_device"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesIP address or hostname of the device
usernameYesUsername for authentication
passwordYesPassword for authentication
device_typeNoPlatform driver: 'cisco_ios' (default), 'bdcom', or any netmiko device_type (e.g. cisco_xe, cisco_nxos, arista_eos). BDCOM switches must use 'bdcom'.cisco_ios
protocolNoConnection protocol (ssh or telnet)ssh
portNoPort number (default: 22 for SSH, 23 for Telnet)
enable_passwordNoEnable password for privileged mode (optional)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description must disclose behavior. It mentions a persistent connection but omits details like failure handling, connection lifecycle, or security implications.

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 concise sentences, front-loaded with core functionality. No extraneous information.

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?

While output schema likely covers return values, the description lacks context on error handling, connection limits, or setup requirements for a parameter-rich tool.

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

Parameters3/5

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

Schema coverage is 100%, so parameters are already well-documented. The description adds no additional parameter context, meeting baseline expectations.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool connects to a network device via SSH or Telnet and establishes a persistent connection. It is distinct from siblings like disconnect_device and execute_command.

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 guidance on when to use this tool versus alternatives like list_connections or execute_command. The description does not mention prerequisites or workflow integration.

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

Deploy Server

Other Tools