Skip to main content
Glama
Sign In

EXZA Remote

by de.exza.remote
OverviewDiscussionsAdmin

Stop interactive process

exza_stop_interactive_process
Destructive

Stop one EXZA-owned interactive process by its session ID; unfinished work may be lost. For a background job use exza_stop_background_job. Requires account-bound computer:write OAuth and any prompted local owner approval.

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": {
      "id": "<id>"
    },
    "name": "exza_stop_interactive_process"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesIdentifier returned by the corresponding start/list operation; not a device PIN.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructive=true and non-idempotent, but the description adds real context: 'unfinished work may be lost' and the auth prerequisites ('account-bound computer:write OAuth and any prompted local owner approval'). It does not cover what happens to the process output buffer, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three facts in two short sentences, front-loaded with the action and scope, then the alternative, then prerequisites. Nothing is redundant with the annotations or schema.

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 destructive one-param mutation with no output schema, the description covers loss risk, the sibling alternative, and auth requirements. A note on whether the process is terminated gracefully or forcibly would make it fully complete.

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 schema already explains that 'id' comes from the start/list operation and is not a device PIN. The description only restates it as 'session ID', adding marginal meaning beyond the schema, so baseline 3 is appropriate.

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+resource+scope: 'Stop one EXZA-owned interactive process by its session ID.' The 'interactive process' qualifier immediately separates it from the many file/desktop siblings, and it names the exact input key.

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

Usage Guidelines5/5

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

Explicitly routes the agent to the alternative: 'For a background job use exza_stop_background_job.' That is a concrete when/when-not split with the sibling named, leaving no ambiguity about which stop tool to pick.

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

All EXZA Remote 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