Skip to main content
Glama
QiuwenZheng

interminal

by QiuwenZheng

respond

Destructive

Send text input to an active command's stdin to answer prompts, provide passwords, or execute shell commands. Returns output or completion status.

Instructions

Write text to a running command's stdin. Works for prompts (y/n,
passwords), shell input, or any text the process expects.

PARAMETER GUIDANCE: text auto-appends \n if missing. For control
keys use send_control — AI frameworks strip control bytes. Raise
pause_timeout (not total_timeout) for slow responses after input.
Raises ValueError if command_id is invalid or completed.

WHEN NOT TO USE: Inside zellij, prefer multiplexer CLI via execute.

SIDE EFFECTS: Writes to stdin; may trigger output, state change, or exit.

RETURNS:
- {"status": "partial", "output": str, "command_id": str}
- {"status": "completed", "output": str, "exit_code": int}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesText to write to stdin (e.g. 'y', a password, a shell command)
command_idYesThe command_id from a status='partial' response. Raises ValueError if invalid or already completed
pause_timeoutNoSeconds of silence before returning (> 0, ≤ total_timeout)
total_timeoutNoHard cap on call duration in seconds (≥ pause_timeout)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed4 schema fields changedv1.0.12
    • changedInput schema / properties / command_id / description
      Previous value: -"The command_id from a status='partial' response. Must be an active (not yet completed) command. Raises ValueError if invalid or already finished"New value: +"The command_id from a status='partial' response. Raises ValueError if invalid or already completed"
    • changedInput schema / properties / pause_timeout / description
      Previous value: -"Seconds of output silence before returning. Raise this (not total_timeout) when the command is slow to respond after receiving input. Must be > 0 and ≤ total_timeout"New value: +"Seconds of silence before returning (> 0, ≤ total_timeout)"
    • changedInput schema / properties / text / description
      Previous value: -"Text to write to the command's stdin (e.g. 'y', a password, a shell command). A trailing newline is auto-appended if missing. For control keys (Ctrl+C, arrows, etc.) use send_control instead — AI frameworks strip control bytes from strings"New value: +"Text to write to stdin (e.g. 'y', a password, a shell command)"
    • changedInput schema / properties / total_timeout / description
      Previous value: -"Hard cap on total call duration in seconds. Only binds while output is actively streaming. Must be ≥ pause_timeout"New value: +"Hard cap on call duration in seconds (≥ pause_timeout)"
  2. Changed4 schema fields changedv1.0.9
    • changedInput schema / properties / command_id / description
      Previous value: -"The active command_id returned in a partial status response that is waiting for input"New value: +"The command_id from a status='partial' response. Must be an active (not yet completed) command. Raises ValueError if invalid or already finished"
    • changedInput schema / properties / pause_timeout / description
      Previous value: -"Seconds of output silence to wait before returning (default is 9.0)"New value: +"Seconds of output silence before returning. Raise this (not total_timeout) when the command is slow to respond after receiving input. Must be > 0 and ≤ total_timeout"
    • changedInput schema / properties / text / description
      Previous value: -"The text input to send to the command (e.g. 'y' for prompts, passwords, etc.). Newline is auto-appended"New value: +"Text to write to the command's stdin (e.g. 'y', a password, a shell command). A trailing newline is auto-appended if missing. For control keys (Ctrl+C, arrows, etc.) use send_control instead — AI frameworks strip control bytes from strings"
    • changedInput schema / properties / total_timeout / description
      Previous value: -"Hard cap in seconds on the maximum duration of this call (default is 20.0)"New value: +"Hard cap on total call duration in seconds. Only binds while output is actively streaming. Must be ≥ pause_timeout"
  3. Changed4 schema fields changedv1.0.3
    • addedInput schema / properties / command_id / description
      Added value: +"The active command_id returned in a partial status response that is waiting for input"
    • addedInput schema / properties / pause_timeout / description
      Added value: +"Seconds of output silence to wait before returning (default is 9.0)"
    • addedInput schema / properties / text / description
      Added value: +"The text input to send to the command (e.g. 'y' for prompts, passwords, etc.). Newline is auto-appended"
    • addedInput schema / properties / total_timeout / description
      Added value: +"Hard cap in seconds on the maximum duration of this call (default is 20.0)"
  4. First observedv0.1.0

TDQS

A5/5.0
Behavior5/5

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

Discloses side effects (writes to stdin, may trigger output/state change/exit), auto-appends newline, and raises ValueError for invalid/closed commands. Complements annotations (destructiveHint=true) with actionable behavioral details.

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?

Well-structured with labeled sections (parameter guidance, when not to use, side effects, returns). Every sentence adds necessary information without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, description fully explains return values with status/output/exit_code structure. Covers error conditions and parameter interactions thoroughly.

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

Parameters5/5

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

Adds value beyond 100% schema coverage by explaining auto-appending newline, recommending send_control for control codes, and clarifying pause_timeout/total_timeout usage. Each parameter gets contextual usage guidance.

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?

Description clearly states 'Write text to a running command's stdin' with specific verb and resource. Distinguishes from sibling send_control for control keys and execute for starting commands.

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

Usage Guidelines5/5

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

Explicitly provides 'WHEN NOT TO USE' clause (inside zellij) and guidance for parameter adjustments (pause_timeout vs total_timeout). Clearly contrasts with send_control for alternative input methods.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/QiuwenZheng/interminal'

If you have feedback or need assistance with the MCP directory API, please join our Discord server