Skip to main content
Glama
Sign In
ibmi-mcp

ibmi-mcp

by WhitehornLtd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

read_screen

Retrieve the current 5250 screen content as structured data including visible text, cursor position, and input fields.

Instructions

Read the current 5250 screen content.

Returns structured data with:

  • screen: list of text rows (the visible display)

  • cursor: current cursor position {row, col} (1-based)

  • fields: list of input fields with position, length, value, and type

  • dimensions: screen size {rows, cols}

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior2/5

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

No annotations provided. The description mentions return structure but does not disclose side-effect behavior (e.g., read-only nature, safety). It lacks explicit transparency beyond output details.

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?

Very concise with bullet-pointed return values. Front-loaded purpose, every sentence adds value. No redundancy.

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

Completeness5/5

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

For a zero-parameter read tool, the description fully explains behavior and return format. No missing details given the simplicity.

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

Parameters4/5

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

No parameters exist, so schema coverage is 100%. Baseline for zero parameters is 4. Description adds no parameter-specific meaning, but none needed.

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

Purpose5/5

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

The description clearly states it reads the current 5250 screen content with a specific verb and resource. It distinguishes itself from sibling tools (connect, disconnect, send_key, etc.) which handle connection and input operations.

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?

The description does not explicitly state when to use this tool versus alternatives, but the purpose is self-explanatory given sibling differentiation. Implicitly requires connection but no explicit guidance.

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