Skip to main content
Glama

read_screen

Retrieve the current terminal screen contents as text. Use it to inspect what an SSH session is displaying before deciding next steps.

Instructions

What the session's terminal shows now, as text.

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

Input Schema

NameRequiredDescriptionDefault
session_idYesA session_id from open_session or list_sessions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full burden. "Shows now" and "as text" do imply a non-destructive point-in-time snapshot rather than scrollback, which is useful, but there is no disclosure of truncation limits, ANSI/escape handling, whether it blocks waiting for output, or permission requirements on the session.

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?

One short sentence, front-loaded with the resource and no filler. It reads as a fragment rather than a complete clause, which costs a little clarity, but nothing in it is wasted.

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 one-parameter read tool with no output schema, the essentials are present: it says the return is text and that it reflects the present screen. Still, an agent cannot tell how much output to expect, whether it is capped, or how it differs from inspecting command output, and no annotations compensate.

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 coverage is 100% and the single parameter's description already points to open_session and list_sessions as sources, so the schema does the work. The tool description adds nothing about session_id, which is the expected baseline 3 when the schema is fully documented.

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 names a specific resource and scope: the current contents of a session's terminal, returned as text. That distinguishes it from siblings like read_file (filesystem) and run_command (execution) by resource alone, though it never explicitly contrasts itself with any sibling.

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 when-to-use guidance at all: nothing says whether to call this after send_input or run_command to check output, whether it replaces reading command results, or whether it is a one-shot snapshot. The word "now" weakly implies a point-in-time read, but no alternative is named and no condition is given.

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