Skip to main content
Glama
Sign In
Agent Guild

Agent Guild

by oddessentials
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Read a terminal

read_screen
Read-only

Retrieves the current plain-text contents of a session's terminal screen so you can see prompts or questions the tool is waiting on.

Instructions

The text a session's terminal shows right now, as plain lines. Use it to see a question the tool is waiting on.

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_idYesThe session id from list_sessions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely useful behavior: the result is a point-in-time snapshot ("right now") and is rendered as plain lines rather than raw terminal escape sequences. It says nothing about what happens when the session is stopped, whether scrollback is included, or how much text is returned.

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, front-loaded with what the tool returns, with no filler. The second sentence is terse to the point of slight ambiguity, but nothing is wasted.

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?

For a one-parameter read-only tool with full schema coverage and annotations carrying the safety profile, the description covers the essential question of what comes back. Edge-case behavior (stopped session, output size limits, scrollback) is unaddressed but is secondary for a simple snapshot read.

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?

There is a single parameter with 100% schema description coverage, pointing the agent at list_sessions for the id. The phrase "a session's terminal" confirms the id selects which terminal is read, but no additional semantics beyond the schema are offered. Baseline 3 is appropriate when the schema already does the documentation.

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 text a session's terminal currently displays, returned as plain lines. That distinguishes it from the read_replies/read_reply siblings, which concern replies rather than terminal output. It stops short of explicitly contrasting itself with any sibling by name, so it lands at a solid 4 rather than 5.

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?

"Use it to see a question the tool is waiting on" gives one concrete usage scenario, which is better than nothing. However, there is no guidance on when not to use it, no mention of alternatives such as list_sessions to find the id first, and "the tool" is ambiguous about which process is being observed.

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

Deploy Server

Other Tools