Skip to main content
Glama
Echoqili

ssh-licco

by Echoqili
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ssh_session

Manage persistent remote screen/tmux sessions for long-running tasks. Create, send commands, capture output, list, or kill sessions that survive SSH disconnects.

Instructions

Manage persistent screen/tmux sessions on the remote server for long-running interactive tasks (deploy, build, test, REPL). Sessions survive SSH disconnect. Actions: create (new detached session running a command), send (send keys/command to a session), capture (read current screen), list (list sessions), kill (kill a session).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostNoSSH server hostname or IP. Alternative to session_id/host_name, can override hosts.json entry.
nameNoSession name. Required for create/send/capture/kill. Only letters, digits, _, ., - allowed.
portNoSSH port (used with host).
linesNoNumber of lines to capture (tmux capture-pane -S).
actionYescreate=new detached session, send=send keys/command to a session, capture=read current screen content, list=list sessions, kill=kill a session.
commandNoCommand to run initially (create) or to send (send).
passwordNoSSH password (used with host).
usernameNoSSH username (used with host).
host_nameNoUse a pre-configured host from hosts.json by name. Alternative to session_id.
session_idYesActive SSH session ID. If omitted, connects via name/host/env vars.
session_typeNoUse screen or tmux backend.screen

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.7.2

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are present, so the description must carry the behavioral burden. It discloses persistence and action meanings (create is detached, capture reads current screen), but does not mention the destructive irreversibility of kill, authentication needs, session/host precedence, or edge-case behavior on nonexistent sessions.

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 tight sentences: the first front-loads purpose and context, the second compactly enumerates all actions. Every sentence earns its place with no filler or redundancy.

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?

The schema is rich and fully covers parameters, and the description covers the tool's overall behavior and all actions. However, with no output schema, it leaves gaps around return format for capture/list, which connection identity (session_id vs host_name vs host) takes precedence, and whether kill requires confirmation.

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 description coverage is 100%, with each parameter already documented in the input schema. The description's action list essentially restates the action enum values without adding new parameter-level meaning, so the baseline of 3 applies.

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?

States a specific purpose ('Manage persistent screen/tmux sessions... for long-running interactive tasks') and enumerates the five actions with concrete semantics. Differentiates from siblings by emphasizing persistence and surviving SSH disconnect, which clearly separates it from one-off ssh_execute.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear context: use for long-running interactive tasks like deploy, build, test, and REPL, and notes sessions survive disconnect. Stops short of explicitly naming alternatives or stating when not to use this tool, so it misses the full when/when-not guidance.

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