Skip to main content
Glama
network-terminal-mcp

network-terminal-mcp

by evgenyzh

terminal_read

Read only new output from an active terminal session until quiet or timeout, with no prompt-shape requirement. Continue from the returned offset when output is truncated.

Instructions

Read only new output until quiet or timeout; no prompt shape required.

If truncated, continue with read_output or next_output_offset.

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": {
      "session_id": "<session_id>"
    },
    "name": "terminal_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeoutNo
session_idYes

Output Schema

NameRequiredDescriptionDefault
outputYes
truncatedNo
next_output_offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv0.5.0
    • removedOutput schema / description
      Removed value: -"A bounded slice of freshly read terminal output."
    • removedOutput schema / properties / next_output_offset / anyOf
      Removed value: -[
      -  {
      -    "type": "integer"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedOutput schema / properties / next_output_offset / default
      Removed value: -null
    • addedOutput schema / properties / next_output_offset / type
      Added value: +"integer"
    • removedOutput schema / properties / output / default
      Removed value: -""
    • removedOutput schema / properties / output_offset
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "integer"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": null,
      -  "title": "Output Offset"
      -}
    • removedOutput schema / properties / session_id
      Removed value: -{
      -  "title": "Session Id",
      -  "type": "string"
      -}
    • removedOutput schema / properties / truncated / default
      Removed value: -false
    • changedOutput schema / required
      Previous value: -[
      -  "session_id"
      -]New value: +[
      +  "output"
      +]
    • changedOutput schema / title
      Previous value: -"TerminalOutput"New value: +"ReadReply"
  2. Changed1 schema field changedv0.2.1
    • addedInput schema / additionalProperties
      Added value: +false
  3. First observedv0.1.1

TDQS

B3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose that only new output is returned, that the call waits for quiet or a timeout, and that results can be truncated, but it never explains what 'quiet' means, what units or default the timeout uses, or whether the read is purely non-destructive.

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?

Two short sentences with the core behavior front-loaded and a concrete recovery path for truncation. The phrase 'no prompt shape required' is cryptic and spends words without adding clarity.

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?

An output schema exists, so return-value documentation is not required, and the truncation fallback is a useful pointer. Still, for a two-parameter tool with zero schema description coverage, the missing timeout semantics and undefined session_id leave the agent guessing at invocation details.

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

Parameters2/5

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

Schema description coverage is 0% for both parameters, so the description must compensate and does not. session_id is never mentioned, and timeout appears only as a bare concept with no units, default, or meaning for null.

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 gives a specific verb plus resource with a scope qualifier: it reads 'only new output' from a terminal session 'until quiet or timeout'. That distinguishes it from the write-side siblings, though the relationship to the sibling read_output remains muddy because it is only mentioned as a truncation fallback.

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?

Usage is implied rather than stated: the agent learns it reads incremental output and blocks until quiet or timeout, and that read_output or next_output_offset should be used when truncated. There is no explicit when-to-use/when-not statement versus read_output, and 'no prompt shape required' is asserted without explaining what the alternative would be.

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