Skip to main content
Glama

get_screen

Read-only

Reads the current IBM i 5250 screen, including row/column rulers, cursor position, keyboard state, screen ID, and input fields to support navigation, data entry, and automated testing.

Instructions

Read the current screen: text with row/column rulers, cursor, keyboard state, screen_id and the input fields.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_screen"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoinclude the input field table
sessionNosession name; lets you run several side by sidemain

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a non-destructive read, so the description's marginal duty is small. It does add useful detail about what 'the current screen' actually contains (row/column rulers, keyboard state, screen_id), but says nothing about snapshot timing, size limits, or whether the read is instantaneous versus awaiting a repaint. Reasonable but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence: the core action first, then the payload contents. Nothing is padded and every listed item conveys what the agent will receive.

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 two-parameter read tool with an output schema, readOnly annotations, and full schema coverage, the description covers the essentials. The remaining gap is routing: nothing tells the agent when this is preferable to 'viewer', 'get_session_log', or 'wait'.

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 100%, so both parameters (fields, session) are already documented in the schema, which sets the baseline at 3. The description's mention of 'the input fields' loosely ties to the fields toggle but adds no conditional logic beyond what the schema states, and 'session' is unaddressed.

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?

Specific verb-plus-resource ('Read the current screen') followed by an enumeration of what the read returns: rulers, cursor, keyboard state, screen_id, input fields. That is far more than a restatement of the name. It stops short of distinguishing itself from plausible near-neighbors such as 'viewer' or 'get_session_log', which an agent would have to resolve by inspecting those tools.

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 only implied: an agent can infer this is the way to observe current terminal state before deciding what to fill or press. There is no explicit when-to-use statement, no exclusion of alternative observation tools, and no guidance on whether to poll with this versus blocking on 'wait'.

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