Skip to main content
Glama

desktop_status

Read-only

Retrieve the desktop hostname, approved roots, and enabled capabilities to verify a client's access scope before running jobs or enabling writes.

Instructions

Return desktop hostname, roots, and enabled capabilities

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.3.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description's contribution is enumerating the returned fields (hostname, roots, enabled capabilities), which matters because there is no output schema, but it does not explain what "roots" or "capabilities" mean or in what form they arrive.

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 sentence with the returned data front-loaded and no filler. It is efficient, though the terse phrasing leaves terms like "roots" and "capabilities" unexpanded for an agent unfamiliar with the host model.

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, read-only info tool with full annotation coverage, the description supplies the one thing structured data does not: which values come back. No output schema exists, and the field list largely closes that gap; only the shape/format of those values is left open.

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 for the description to add and the baseline of 4 applies. The schema is an empty object with additionalProperties=false, consistent with the description's parameterless framing.

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?

"Return desktop hostname, roots, and enabled capabilities" pairs a specific verb with the exact data items returned, so an agent knows this is a read-only environment-info call rather than a GUI/browser action. It stops short of naming any sibling (e.g. browser_snapshot, list_directory) to sharpen the boundary, so it is clear but not sibling-differentiated.

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?

The description gives no when-to-use guidance: nothing says whether to call this first to discover roots before list_directory/read_text_file, or how it relates to the gui_*/browser_* action tools. Usage is only inferable from the word "status", which is the kind of implied-but-unstated context the guideline band of 2 covers.

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