Skip to main content
Glama

desktop_list_surfaces

Lists accessibility surfaces (windows, menus, sheets) for an app so MCP clients can identify UI targets before acting.

Instructions

agent-desktop list-surfaces: List accessibility surfaces for an app (window, menu, sheet ...)

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

Input Schema

NameRequiredDescriptionDefault
appNoFilter to application by name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It implies a read operation via "List" but says nothing about behavior when the app name does not match, whether the app parameter is effectively required for meaningful results, or how large the surface set can be.

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 compact sentence, front-loaded with the operation. The "agent-desktop list-surfaces:" prefix partially restates the tool name, which is minor waste, and the trailing ellipsis leaves the enumeration open-ended.

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 (one optional parameter, no output schema), but the description never says what a returned surface looks like or how it would be used downstream, and the "..." truncation leaves the set of surface types ambiguous. Adequate to call, not adequate to interpret results.

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 100% for the single optional "app" parameter, so the baseline is 3. The parenthetical examples of surface kinds add meaning about the resource rather than the parameter, and no additional guidance on the app filter (exact match, partial name) is provided.

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?

"List accessibility surfaces for an app" gives a specific verb (list) and resource (accessibility surfaces), with examples (window, menu, sheet) that make the concept concrete. It does not distinguish itself from the close sibling desktop_list_windows, so an agent cannot tell from the description alone which one to reach for.

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 when-to-use or when-not-to-use guidance, and no alternatives are named even though desktop_list_windows and desktop_list_apps overlap conceptually. The agent must infer the use case entirely from the tool name.

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