Skip to main content
Glama

read_window

Read a window's controls one per line with refs for click and set_text, enabling an AI agent to inspect and operate Windows applications.

Instructions

The window's controls, one per line, each with a ref (e1, e2, ...) for click and set_text.

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": {
      "handle": "<handle>"
    },
    "name": "read_window"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It discloses the output structure (one control per line, refs like e1/e2) and explains that those refs are used by click and set_text, which is meaningful context. It does not confirm read-only behavior, error handling for bad handles, or how many controls are returned, so key behavioral traits remain undisclosed.

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?

The description is a single tight sentence with no wasted words, and the core information about controls and refs is front-loaded. It is somewhat telegraphic, but appropriately sized for a simple tool.

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

Completeness3/5

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

The tool is simple, has one parameter, and includes an output schema, which lowers the description burden. The description explains the output refs and their downstream use, but it omits any explanation of the required handle parameter and does not help distinguish this from list_windows. Those gaps keep it from being fully complete.

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

Parameters2/5

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

There is one required parameter, handle, with 0% schema description coverage. The description never mentions handle or explains what it identifies, so it fails to compensate for the schema gap. The agent can infer it refers to a window from context, but the parameter semantics are essentially undocumented.

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 that it returns the window's controls, one per line, with refs for click and set_text. This clearly identifies the resource and output shape, and distinguishes it from the sibling click/set_text tools by framing refs as inputs to them. It does not explicitly say 'read' or 'get', but the name and content make the purpose clear.

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: read a window to obtain refs that can then be passed to click or set_text. However, there is no explicit guidance on when to use this versus list_windows, nor any exclusions or prerequisites. The workflow connection is useful but still leaves the agent to infer the selection rule.

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