Skip to main content
Glama

desktop_watch_stop

Stops a live desktop observation session by session ID and releases its resources, ending monitoring when the session is no longer needed.

Instructions

Stop a live desktop observation session and release its resources.

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

Input Schema

NameRequiredDescriptionDefault
session_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.7/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 behavioral burden. It discloses only that resources are released; it says nothing about idempotency, behavior when the session is unknown, whether other watchers are affected, or what is returned on success or failure.

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 front-loaded sentence with no filler; the action is stated first and the side effect second. It is short, but its brevity comes at the cost of the missing details noted above rather than from tight editing.

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 low-complexity tool with no annotations and no output schema, the description should still resolve the optional session_id default and failure/idempotency behavior. Neither is covered, leaving an agent unable to predict what calling it with no arguments does.

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?

The schema has one parameter with 0% description coverage, and the description never mentions session_id at all. Because the parameter is optional with an empty-string default, the description should clarify whether an empty value stops the current/only session or all sessions — that ambiguity is unresolved.

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 (stop) and resource (a live desktop observation session) plus a secondary effect (release its resources). It contrasts implicitly with desktop_watch_start/desktop_watch_read through the verb, though it never names an alternative explicitly.

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?

No guidance on when to call this versus leaving a session running, nor on prerequisites such as whether a session must currently be active. The critical question of what happens when session_id is omitted (its default is an empty string) is left entirely unaddressed.

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