Skip to main content
Glama

Send Input

send_input

Deliver text input to a running asynchronous SSH command and return new output, enabling replies to prompts, pager controls, and interactive programs.

Instructions

Send input to a running async command and return any new output.

Useful for interacting with commands that require user input, such as:
- Pagers (less, more): send 'q' to quit, space to page down
- Yes/no prompts: send 'y' or 'n'
- Interactive programs: send appropriate responses

Args:
    command_id: The command ID to send input to
    input_text: Text to send (e.g., 'q', 'y

', etc.)

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": {
      "command_id": "<command_id>",
      "input_text": "<input_text>"
    },
    "name": "send_input"
  }
}

Input Schema

NameRequiredDescriptionDefault
command_idYes
input_textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2+p1

TDQS

B3.4/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden. It discloses only that new output is returned; it says nothing about whether a newline is appended automatically, whether the call blocks or waits for output, timeouts, or what happens if command_id is invalid or the command has already exited — all critical for an input-injection tool.

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?

Front-loaded with the core action in the first sentence, followed by scannable bullet examples. The trailing Args block largely restates the schema, adding modest length, but nothing is padding.

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 two-parameter, no-annotation, no-output-schema tool, the description covers what to send but not enough of the interaction contract (blocking, timeouts, error cases, newline semantics) for an agent to call it reliably in edge cases.

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 0%, so the description must compensate, and it does partially: both parameters are named with one-line glosses and input_text gets illustrative values ('q', 'y\n'). However, the example implies newline handling matters without explaining it, and command_id's provenance (where to obtain an ID — e.g., from execute_command_async) is left unstated.

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 first sentence states a specific verb and resource ("Send input to a running async command") and adds the return behavior ("return any new output"), which distinguishes it from read-only siblings like read_screen or get_command_status. It doesn't explicitly differentiate from close-sounding siblings such as send_keys or send_input_by_session, but the async-command framing is specific enough for selection.

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?

Concrete when-to-use context is given: pagers (less/more), yes/no prompts, and interactive programs, each with a sample payload. There are no exclusions or pointers to alternatives (e.g., when to use send_keys vs this tool), which keeps it at 4 rather than 5.

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