Skip to main content
Glama

desktop_is

Checks whether a UI element is visible, enabled, checked, focused, expanded, or selected using its snapshot reference, so agents can verify interface state before or after actions.

Instructions

agent-desktop is: Check element state (visible, enabled, checked, focused, expanded, selected)

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": {
      "ref_id": "<ref_id>"
    },
    "name": "desktop_is"
  }
}

Input Schema

NameRequiredDescriptionDefault
ref_idYesQualified ref from snapshot (@<snapshot_id>:eN)
propertyNoState: visible, enabled, checked, focused, expanded, selectedvisible

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.8/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 burden. It does not state that this is a non-mutating read, what the tool returns (a boolean, the state value, or all states), or how it behaves for an invalid ref_id or a state property that doesn't apply to the element.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The body is a single economical clause, but the leading "agent-desktop is:" fragment is noise that pushes the actual purpose back and could read as a namespace artifact. The key content is front-loaded only after that dead phrase.

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

Completeness2/5

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

For a query tool with no annotations and no output schema, the description must convey what comes back and how to interpret it; it does neither. An agent knows what to ask for but not what it receives or how to handle ref/property mismatches.

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 coverage is 100%, so both ref_id and property are documented in the schema, and the schema already lists the exact same six state values that the description repeats. The description adds no meaning beyond the schema, making baseline 3 appropriate.

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?

"Check element state" is a specific verb+resource pair that tells an agent this is a read-style query about a UI element's state. However, the awkward "agent-desktop is:" prefix leaks framing text into the definition, and there is no differentiation from siblings like desktop_check or desktop_get, so an agent cannot tell these apart from the description alone.

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. With desktop_check, desktop_get, and desktop_find in the sibling set, some routing hint (e.g., "use this after a snapshot to confirm a state") would be valuable, but none is given.

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