Skip to main content
Glama
Sign In

Remote Desktop Commander

by app.desktopcommander
OverviewDiscussionsAdmin

stop_search

                    Stop an active search.
                    
                    Stops the background search process gracefully. Use this when you've found
                    what you need or if a search is taking too long. Similar to force_terminate
                    for terminal processes.
                    
                    The search will still be available for reading final results until it's
                    automatically cleaned up after 5 minutes.
                    
                    This command can be referenced as "DC: ..." or "use Desktop Commander to ..." in your instructions.

Input Schema

NameRequiredDescriptionDefault
deviceIdNoThe ID of the device to run this tool on (from list_devices). Required when more than one device is online; may be omitted when only one device is connected.
sessionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-destructive, closed-world behavior, and the description adds genuinely new context: the stop is graceful and results remain readable for 5 minutes until automatic cleanup. That lifecycle detail is not derivable from the annotations and materially affects follow-up behavior. It doesn't state what happens if the sessionId is invalid or already stopped.

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?

Front-loaded with the core action, followed by usage conditions and lifecycle behavior in a sensible order. The trailing 'DC: ...' invocation boilerplate is generic across the server and adds little, but overall the text is tight.

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 two-parameter stop tool with annotations and no output schema, the behavioral picture is mostly complete, but the missing guidance on sourcing the required sessionId and on the return/error behavior leaves a real gap an agent would hit on first invocation.

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 coverage is only 50%: deviceId is documented in the schema, but the required sessionId has no description anywhere. The description never explains what a sessionId is or where to get one, so it fails to compensate for the coverage gap on the one mandatory parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Stop an active search') and explicitly contrasts itself with the sibling force_terminate, which handles terminal processes rather than searches. An agent can distinguish it from start_search and force_terminate without opening any schema.

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

Usage Guidelines4/5

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

Gives concrete when-to-use conditions ('when you've found what you need or if a search is taking too long') and names the analogous sibling force_terminate. It stops short of saying how to obtain a sessionId (e.g., via list_searches) or when not to call it, but the invocation context is clear.

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

All Remote Desktop Commander toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources