Skip to main content
Glama

read_windows

Read-only

Lists open desktop windows with ID, app, title, focus state, and workspace so AI agents can identify and target the correct window.

Instructions

Open windows, one per line: id, app, title, focused, workspace.

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_windows"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds value beyond them by disclosing the return shape (one window per line with id, app, title, focused, workspace), which matters because no output schema exists.

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?

A single front-loaded line listing the payload fields, with no filler. The opening phrase 'Open windows' is verbless and briefly ambiguous (it can parse as an imperative), which costs it the top score.

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?

Because there is no output schema, the field list is essential and present, but the description says nothing about ordering, whether 'focused' is a boolean or id, how empty results appear, or scope across workspaces. For a zero-parameter read tool this is adequate but leaves real gaps.

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 no parameter meaning to document and the baseline is 4. The description correctly implies the call needs no arguments to enumerate all windows.

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 names the resource (open windows) and enumerates the fields returned, so an agent can tell it lists windows rather than acting on one. It does not differentiate itself from the sibling read_window (singular) or explain whether it covers all desktops/workspaces.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no mention of read_window, read_status, or act_window as alternatives. The agent must infer that this is the bulk listing variant versus the singular reader.

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