Skip to main content
Glama
network-terminal-mcp

network-terminal-mcp

by evgenyzh

session_status

Returns terminal session state, current command, timestamps, idle time, warnings, and exit status so you can monitor progress and detect stalled or failed device sessions.

Instructions

Return state, command, timestamps, idle time, warnings, and exit status.

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": "session_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYes

Output Schema

NameRequiredDescriptionDefault
errorNo
stateYes
commandYes
warningsNo
exit_codeNo
created_atYes
session_idYes
idle_secondsNoSeconds since the last output, or since session creation when no output has arrived yet.
last_used_atYes
last_output_atNoUTC timestamp when output was last received; null if the session has not produced any output yet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv0.2.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedOutput schema / properties / command
      Added value: +{
      +  "title": "Command",
      +  "type": "string"
      +}
    • addedOutput schema / properties / error
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Error"
      +}
    • addedOutput schema / properties / exit_code
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Exit Code"
      +}
    • removedOutput schema / properties / host
      Removed value: -{
      -  "title": "Host",
      -  "type": "string"
      -}
    • addedOutput schema / properties / idle_seconds
      Added value: +{
      +  "default": 0,
      +  "description": "Seconds since the last output, or since session creation when no output has arrived yet.",
      +  "minimum": 0,
      +  "title": "Idle Seconds",
      +  "type": "number"
      +}
    • addedOutput schema / properties / last_output_at
      Added value: +{
      +  "anyOf": [
      +    {
      +      "format": "date-time",
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "UTC timestamp when output was last received; null if the session has not produced any output yet.",
      +  "title": "Last Output At"
      +}
    • removedOutput schema / properties / prompt
      Removed value: -{
      -  "default": "",
      -  "title": "Prompt",
      -  "type": "string"
      -}
    • removedOutput schema / properties / route
      Removed value: -{
      -  "title": "Route",
      -  "type": "string"
      -}
    • changedOutput schema / required
      Previous value: -[
      -  "session_id",
      -  "route",
      -  "host",
      -  "state",
      -  "created_at",
      -  "last_used_at"
      -]New value: +[
      +  "session_id",
      +  "command",
      +  "state",
      +  "created_at",
      +  "last_used_at"
      +]
  2. First observedv0.1.1

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden, yet it never states that this is a read-only, side-effect-free operation. It mentions 'idle time' and 'warnings' without explaining what they mean or how they are computed, and says nothing about blocking behavior, cost, or what happens if the session has exited. Enumerating return fields adds little because an output schema already exists.

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?

A single compact sentence with no filler or redundancy. It is front-loaded with the verb, though the content is a flat field list rather than a prioritized statement of purpose.

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

Completeness2/5

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

The presence of an output schema reduces the need to explain return values, but the definition still omits the session_id semantics, any read-only assurance, and any differentiation from read_output and terminal_read. For a tool in a crowded session/terminal sibling set with zero annotations, this leaves too much to inference.

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% and the sole parameter, session_id, is never mentioned in the description. The agent gets no information about the expected format, where to obtain a session_id, or whether it must come from open_session. With one undocumented parameter, the description does not compensate for the schema gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says it 'Returns state, command, timestamps, idle time, warnings, and exit status,' which is essentially an enumeration of return fields rather than a statement of what the tool is for. It never says this is the status of a terminal/shell session identified by session_id, so an agent must infer the resource from the tool name and sibling list. It is closer to a field list than a clear verb+resource purpose.

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 guidance on when to call this versus read_output, terminal_read, or open_session, all of which could plausibly surface session information. No prerequisites, no mention that the session must be open, and no indication of whether this is a polling call or a one-shot snapshot. The agent is left to infer everything from the name.

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