Skip to main content
Glama

desktop_status

Check adapter health, platform details, and permission status to diagnose desktop access issues before running window inspection or UI actions.

Instructions

agent-desktop status: Show adapter health, platform info, and permission state

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does convey that this is a passive inspection of adapter health and permission state, with no parameters and therefore no mutation path. It stops short of stating that it is strictly read-only, what the response shape is, or what an unhealthy adapter result implies for subsequent calls.

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 short line with the returned data front-loaded and no wasted sentences. The "agent-desktop status:" prefix duplicates the tool name and contributes little beyond vendor context.

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?

For a zero-parameter, zero-annotation tool with no output schema, the description should sketch what comes back; it names three result categories but not their format or structure. It is nearly sufficient but leaves the agent guessing about the response shape.

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 convey; the baseline applies and nothing in the description conflicts with the empty schema.

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 gives a concrete verb ("Show") and enumerates the specific resources returned: adapter health, platform info, and permission state. It is clearly a read-only introspection tool, but it does not explicitly distinguish itself from near-neighbors such as desktop_check, desktop_is, or pilot_request_status.

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 statement of when to call this versus desktop_check or desktop_is, and no guidance on calling it before desktop operations to verify permissions. The usage is only inferable from the word "status".

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