Skip to main content
Glama

List desktop windows

list_windows
Read-onlyIdempotent

Lists open desktop windows by app and title, helping you select the correct window as a screenshot source; requires the Recordful desktop app with AI agents enabled.

Instructions

List the windows open on the desktop (app and title, no pictures), for take_screenshot with source "window". Needs the Recordful desktop app with AI agents turned on in its Settings.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety needs no restating. The description adds real value beyond them: the prerequisite that the Recordful desktop app must be running with AI agents enabled in Settings, plus the fact that no image data is returned — both failure-mode details the annotations cannot convey.

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?

One sentence, front-loaded with what is listed, then the return fields, then the pairing and prerequisite. Nothing is repeated and no filler is present.

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 no parameters and no output schema, the description carries the burden well by naming the returned fields and the environment prerequisite. It leaves only edge behavior (empty desktop, error when the app or AI-agent setting is missing) unstated, which is a minor gap for a simple read-only list.

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 the baseline is 4; there is nothing for the description to disambiguate. The mention of app and title is return-value information rather than parameter meaning, which is appropriate here.

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?

States a specific verb and resource ("List the windows open on the desktop") and even pre-empts the obvious confusion by clarifying the return shape is "app and title, no pictures". That single parenthetical separates it from the screenshot-oriented siblings without the agent needing to open any schema.

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?

It gives a concrete downstream use case — feed the result to take_screenshot with source "window" — which tells the agent exactly when this tool is the right first step. It does not spell out explicit exclusions (e.g. what to call instead if you want thumbnails or full-screen capture), so it stops short of full routing guidance.

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