Skip to main content
Glama

send_input

Send text input to active interactive sessions (msfconsole, SSH, shell) to execute commands and interact with long-running processes.

Instructions

Send text input to any active interactive session (msfconsole, SSH, mysql, python REPL, shell, etc.). This is a generic primitive that works with ANY session type managed by the backend — it is not limited to Metasploit.

Use this together with read_output() to have a full interactive conversation with a long-running process:

  1. Start a session (e.g. via msf_session_create or zebbern_exec with background=True)

  2. send_input(session_id, "some command\n")

  3. read_output(session_id) to collect the response

Args: session_id: The session identifier returned when the session was created. input_text: The text to send to the session's stdin. Include a trailing newline (\n) if the target process expects one. session_type: Hint for the backend on how to handle the session. 'auto' (default) lets the backend detect the type. Other values: 'msfconsole', 'ssh', 'shell', 'mysql', 'python'.

Returns: dict with at minimum: - success (bool): whether the input was accepted - session_id (str): echo of the session targeted - error (str, optional): present only on failure

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
input_textYes
session_idYes
session_typeNoauto

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description does a good job disclosing key behaviors: it sends input to stdin of any active session, includes a session_type hint, and details the return format. It could be improved by mentioning if the call is blocking or any concurrency concerns, but overall it is sufficient.

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?

The description is well-structured with a clear header, usage steps, parameter list, and return info. It is concise with no unnecessary words, delivering high information density in a compact format.

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

Completeness4/5

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

Given the tool's simplicity and the presence of an output schema (which the description summarizes), the description covers the essential workflow and parameters. It explains the cooperation with read_output and the return values. A minor omission is not explicitly stating that the session must remain active, but this is implied. Overall, it is nearly complete.

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?

The input schema has 0% description coverage, but the description fully compensates with an Args section explaining all three parameters: session_id, input_text (including trailing newline advice), and session_type (default 'auto', other values listed). This adds significant meaning beyond the schema's type/title only.

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 verb 'Send text input' and the resource 'active interactive session', listing examples like msfconsole, SSH, etc. It explicitly distinguishes itself as a generic primitive working with ANY session type, not just Metasploit, which differentiates it from sibling tools like msf_session_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?

The description provides explicit usage guidance by outlining a three-step workflow with read_output() and explains that it works for any session type. However, it does not explicitly mention when not to use this tool or list alternatives beyond read_output.

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

Install Server

Other Tools

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/zebbern/zebbern-kali-mcp'

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