Skip to main content
Glama

viewer

Read-only

Open a live browser session so a human can watch the IBM i 5250 screen, sign on, or take over when a password is required.

Instructions

Link to the live web viewer, where the human can watch, sign on or take over. Give it to the user when a password is needed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/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 safe read, so the description's added value is the human-facing purpose and the password-entry trigger. It does not say whether the link expires, is single-use, or is scoped to the current session, which matters for a hand-off URL.

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, with the deliverable stated first and the hand-off condition second. Wording like "Link to the live web viewer" is slightly clipped but wastes no space.

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?

Output schema exists and there are no parameters, so the description only needs to convey purpose and the human hand-off rule, which it does. Adding link lifetime or one-time-use behavior would close the remaining gap.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline applies. The description adds the relevant nuance that the output is meant to be passed on to the user rather than consumed by the agent.

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 states a concrete deliverable (a link to the live web viewer) and its purpose for the human: watch, sign on, or take over. It is specific enough to separate from siblings like get_screen or connect, though it never names an alternative to contrast with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Give it to the user when a password is needed" is an explicit trigger condition, and the watch/sign-on/take-over framing clarifies the scenario. It stops short of stating when not to use it or which sibling handles adjacent cases.

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