Skip to main content
Glama

Stop remote desktop

stop_remote_desktop

Stop remote desktop access to a browser

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": {
      "address": "<address>"
    },
    "name": "stop_remote_desktop"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesAddress of the browser

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / address / description
      Previous value: -"Dirección del navegador"New value: +"Address of the browser"
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already tell the agent this is not read-only, not destructive, and not open-world, so the description adds little. It never says what happens to the session when access stops (does the browser stay connected, do tabs survive, is the session resumable) or what happens if no session exists.

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, front-loaded sentence with no filler. It is efficiently written, though the brevity comes at the cost of the missing behavioral detail rather than being a model of density.

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 state-changing session tool with no output schema and no annotations covering session semantics, the description leaves key questions unanswered: effect on the browser session, error conditions, and reversibility. It is too thin relative to what an agent needs to call it confidently.

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

Parameters3/5

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

Schema coverage is 100% and the single parameter is documented as "Address of the browser" in the schema itself. The description adds no format detail (URL scheme, browser ID, host:port) or validation behavior beyond that, so the baseline 3 applies.

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 ("remote desktop access to a browser"), which cleanly contrasts with the sibling start_remote_desktop. It does not explicitly name or describe the counterpart, so it falls short of full sibling differentiation.

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 when-to-use guidance, no prerequisites (e.g., must already be connected), and no mention of start_remote_desktop as the way to re-enable access. The agent must infer that this terminates an existing remote deskop session.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources