Skip to main content
Glama

desktop_read_value

Reads the current value of a field in a native desktop window to verify the result after an action.

Instructions

Read the current value of a field in a native window (the verification step).

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": {
      "title": "<title>",
      "control": "<control>"
    },
    "name": "desktop_read_value"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
controlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It does communicate that this is a read-only operation and frames its role as post-action verification, which is meaningful context. It does not disclose whether reading blocks or waits for the field to appear, what happens if the window or control is missing, or what value format is returned.

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?

One short sentence with the core action front-loaded and the role qualifier at the end. There is no wasted wording, though the extreme brevity leaves gaps rather than being padded.

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 two-parameter tool with no annotations, no output schema, and zero parameter documentation, the description is too thin. It does not explain how the window and control are located, what the returned value looks like, or what failure indicates — all information an agent needs to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so both required parameters ('title' and 'control') are bare strings with no documentation. The description does not clarify that 'title' identifies the target window or how 'control' addresses a specific field, so an agent must guess the identification format.

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 states a specific verb and resource: reading the current value of a field in a native window. That is distinguishable from siblings like desktop_click or desktop_type, which mutate state. It stops short of naming those siblings explicitly, so it does not earn a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The parenthetical '(the verification step)' implies the tool is called after a write action to confirm the result, which is a useful hint. However, it gives no explicit when-not guidance, no mention of when to use desktop_inspect or desktop_watch_read instead, and no prerequisites for the verification workflow.

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