Skip to main content
Glama

connect

Opens a 5250 session and returns the first screen, such as Sign On or a profile menu, to start IBM i green-screen work.

Instructions

Open a 5250 session and return the first screen: Sign On, or the screen after the profile's after-connect flow (e.g. a menu once signed on).

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

Input Schema

NameRequiredDescriptionDefault
tlsNo
hostNoIBM i host name, e.g. pub400.com (when not using a profile)
portNo992 for TLS (default), 23 for plain telnet
wideNo27x132 display (3477) instead of 24x80
profileNosaved connection profile (see list_profiles); then leave out the connection details
sessionNosession name; lets you run several side by sidemain
codepageNoEBCDIC code page, e.g. cp037 (US), cp273 (DE), cp500 (intl)
verify_tlsNo
device_nameNoask for a display device name; * becomes A, B, C... per connection (e.g. AGENT*), = a random character

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and destructiveHint=false, so the agent knows this is a non-idempotent, network-touching operation. The description adds real value by explaining what the response will be — Sign On versus the post-profile menu screen — which is non-obvious state-machine behavior. It omits what happens if the session name is already in use or if the host is unreachable, keeping it below 5.

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 dense sentence with a colon-delimited clarification that front-loads the action and then the return value. Every clause carries information; there is no filler or restatement of the name.

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?

With an output schema present, the description needn't enumerate return fields, and it correctly covers the one ambiguity an agent would have — what screen comes back. For a 9-parameter, all-optional session-establishing tool, the remaining gap is its silence on session-name collisions and connection failure behavior.

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 78%, above the 80%-adjacent threshold where the schema already documents host, port, profile, codepage, wide and device_name. The description adds no parameter-level detail beyond echoing 'profile' in prose, so it neither compensates for nor undermines the remaining gap (tls, verify_tls).

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?

States a specific verb and resource ('Open a 5250 session') plus what comes back ('return the first screen'), which is enough to distinguish it from siblings like get_screen or disconnect without opening the schema. It stops short of naming a sibling, so it does not earn a full 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?

Usage is implied (call this to establish a session) but there is no explicit when/when-not guidance or named alternative such as list_profiles or list_sessions for pre-existing sessions. The mention of 'the profile's after-connect flow' hints that a saved profile drives the result, but the agent must infer that from the schema.

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