Skip to main content
Glama

rex_send_text

Sends text to a terminal session and optionally presses Return, enabling AI assistants to submit commands or responses in Rex sessions.

Instructions

Type text into a terminal (rex send, text on stdin). enter: true presses Return afterwards.

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": {
      "text": "<text>"
    },
    "name": "rex_send_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
blockNoBlock label, ID, or ID suffix
enterNo
sessionNoSession label or ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses the core mutation (typing into a terminal) and the key option that `enter: true` presses Return, but it does not explain session requirements, whether text is interpreted, what happens to the terminal state, or what the tool returns.

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 description is short and front-loaded around the main action. The parenthetical `rex send, text on stdin` is slightly implementation-flavored, but there is little wasted wording.

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 simple four-parameter terminal-write tool, the core action and the `enter` behavior are covered. However, the description leaves session/block targeting and side-effect behavior implicit, which matters more because there are no annotations and no output schema.

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 50%. The description adds meaning for `text` by saying it is sent on stdin and for `enter` by saying it presses Return, but it does not add anything for `session` or `block`, which rely on their schema descriptions.

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 clearly states a specific verb and resource: type text into a terminal. It is distinguishable in broad terms from key-sending siblings, but it does not explicitly differentiate itself from rex_send_keys or explain when text versus keys should be used.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no alternative sibling is named. The agent can infer that this tool is for typing text, but it is not told when to prefer it over rex_send_keys, rex_run, or other terminal interactions.

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