Skip to main content
Glama

desktop_list

Read-onlyIdempotent

List the remote desktop sessions (Windows over RDP, Linux or Mac over VNC) open for AI in Termalin (sessions, with what you may do on each: "view" = screenshots only, "control" = also mouse and keyboard), and the desktops the user saved for AI that you can open with desktop_open (desktops). The user started this desktop session for you in Termalin and can watch it. Coordinates are pixels of your last desktop_screenshot. Never type passwords, keys or other secrets: when a sign-in or secret is needed, stop and ask the user to type it themselves.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered; the description adds genuinely new behavior: the capability flags per session and that the user started the session and can watch it, plus a hard constraint never to type secrets and instead stop and ask the user. It does not say anything about result ordering, empty results, or whether sessions can expire, which keeps it from a 5.

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?

Front-loaded with the primary resource and the two returned collections, with parentheses used to attach the per-session capability semantics compactly. The trailing secrets warning is somewhat tangential to a list operation, but it is one sentence and safety-critical rather than filler.

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 output schema, the description carries the burden of explaining what comes back, and it does name both returned collections and the per-session permission meaning. It is missing return ordering/shape details and any note on what an empty list means, but nothing required to invoke this zero-arg tool correctly is absent.

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 and there is no schema gap for the description to compensate for. The description's field-level detail (`sessions`, `desktops`, view vs control) describes return content rather than parameters, which is helpful but not a parameter-semantics contribution.

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 (list) and two concrete resources: `sessions` (open remote desktop sessions, Windows/RDP vs Linux-Mac/VNC) and `desktops` (user-saved desktops). It even names the sibling that consumes the saved desktops (desktop_open), so the agent can separate this tool from the click/key/screenshot family without opening 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?

Clear context: call this to discover sessions and their permission level ("view" = screenshots only, "control" = also mouse and keyboard) and to find saved desktops you can then open with desktop_open. What is missing is an explicit sequencing statement (e.g. "call this first, before desktop_screenshot/desktop_click") and any exclusion for when not to use it, but the alternative routing to desktop_open is spelled out.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.