Skip to main content
Glama

desktop_version

Displays the agent-desktop version, target architecture, and operating system so you can confirm runtime details before inspecting desktop windows or running UI actions.

Instructions

agent-desktop version: Show version, target architecture, and OS

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden. It discloses the three concrete values returned, which implies a read-only, side-effect-free call, but it never says so explicitly and gives no hints about output format or whether the values reflect the server host or the agent runtime.

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, front-loaded line with no wasted words. The 'agent-desktop version:' prefix partially repeats the tool name, a minor redundancy, but it frames the statement efficiently.

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?

For a zero-parameter tool with no output schema and no annotations, the description covers the essentials an agent needs: what is returned. Only minor gaps remain, such as output formatting and whether architecture refers to the host or the client.

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, which is the baseline-4 case. The description's mention of returned fields adds a little orientation ('target architecture' hints at the platform concept) but no parameter meaning is needed.

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?

States a specific verb+resource (report the agent-desktop version) and names the three values returned: version, target architecture, and OS. This clearly distinguishes it from the action-oriented siblings like desktop_list_windows or desktop_focus, though it never explicitly contrasts with any of them.

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 guidance, no prerequisites, and no mention of alternatives or related diagnostic tools. The name and description imply it is an informational call, but an agent must infer on its own that this is for environment/diagnostic checks.

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