Skip to main content
Glama

Send Input By Session

send_input_by_session

Send text or control keys to an active SSH shell session to resolve stuck interactive states or interact with pagers and prompts.

Instructions

Send input to the active shell for a session.

Useful for clearing stuck interactive states or sending input to the current shell.

Args:
    host: Hostname, IP address, or SSH config alias
    input_text: Text to send (e.g., 'q

' to quit pager, '' for Ctrl+C) username: SSH username (optional) port: SSH port (optional)

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>",
      "input_text": "<input_text>"
    },
    "name": "send_input_by_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYes
portNo
usernameNo
input_textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2+p1

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 carries the full behavioral burden, and it discloses only the surface behavior (sends text into an interactive shell). It says nothing about whether a session must already exist and be attached to a shell, what occurs if no active shell is present, whether the call blocks or waits, or any timeout/error behavior. The escape-sequence examples hint at raw input semantics but fall far short of the disclosure this unannotated mutation-style tool needs.

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?

The purpose statement is front-loaded in a single sentence and the Args block is scannable with one line per parameter. The middle 'Useful for...' sentence is somewhat redundant with the opening line, and the block formatting has stray whitespace, but overall the text is efficient.

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?

For a four-parameter tool with no annotations and no output schema, the definition covers purpose and all parameters adequately, but omits the operational context an agent needs: session/shell preconditions, failure modes, and what the call returns or how it interacts with the command lifecycle. The parameter story is complete; the behavioral story is not.

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?

Schema description coverage is 0%, so the description must document all four parameters — and it does, including the non-obvious details: host accepts a hostname, IP, or SSH config alias, and input_text accepts escape sequences with concrete examples ('q\n' to quit a pager, control character for Ctrl+C). Username and port are correctly marked optional. It stops short of noting default values or port constraints, keeping it out of the top band.

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 a specific verb ('Send input') and target ('the active shell for a session'), which an agent can distinguish from the sibling send_input/execute_command family only by the 'for a session' scoping. It states what the tool does concretely, but never explicitly contrasts itself with send_input or send_keys, so the differentiation is inferred rather than stated.

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?

"Useful for clearing stuck interactive states or sending input to the current shell" implies a use context, but it is phrased permissively ('useful for') rather than as a directive. No exclusions or alternative tools are named, and the file lacks any statement of prerequisites such as needing an existing active session, which is the key selection question against siblings like send_input.

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