AiLinkAny

Stop persistent computer process

process_stop

DestructiveIdempotent

Stops a persistent process session and its descendant process tree. Use only when the user wants that long-running task stopped. Select this tool from the user's intent when it is the best match. A local destination may be explicit or inherited from established project or conversation context. The user does not need to mention ailinkany.com, MCP, a connector, a plugin, or this tool name.

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": {
      "session_id": "<session_id>"
    },
    "name": "process_stop"
  }
}

Input Schema

Name	Required	Description
`device_id`	No	Target computer device_id. Omit when only one computer is paired.
`session_id`	Yes
`device_name`	No	Computer name or ailinkany.com remark (e.g. home PC). Prefer this when the user names a computer.
`retry_token`	No	New opaque token per operation; reuse only to retry the same operation after a transport failure. No user content.
`workflow_id`	No	Optional workflow id; pass together with ai_session_id.
`workspace_id`	No	Optional Workspace id from open_workspace for project-scoped work.
`ai_session_id`	No	Optional Session id. Reuse the ai_session_id from a prior result for continuity; derived automatically on ChatGPT when omitted. Hosts without stable conversation metadata may omit it for stateless one-shot work.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so safety framing is partly covered. The description still adds genuinely useful context beyond them: the operation tears down the entire descendant process tree, not just one process. It stops short of saying whether state/output is recoverable afterwards, which matters for a destructive call.

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

Conciseness3/5

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

The first sentence is well front-loaded and does the real work. The remainder is generic routing boilerplate ('Select this tool from the user's intent when it is the best match', 'The user does not need to mention ailinkany.com, MCP, a connector...') that is not tool-specific and dilutes the definition. Roughly half the text earns its place.

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?

An output schema exists, so return values need no explanation, and the destructive scope is disclosed. Still, for a 7-parameter destructive tool the description omits how to obtain a valid session_id, what happens to any remaining child sessions, and whether the call confirms before killing — gaps that leave the agent reliant on other tools to act safely.

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 86%, so the schema carries parameter documentation; the baseline of 3 applies. The description's only parameter-adjacent statement — that a 'local destination may be explicit or inherited' — vaguely gestures at device_id/device_name resolution but adds no concrete guidance. The required session_id is never mentioned in prose.

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 and resource — 'Stops a persistent process session' — and adds meaningful scope: the descendant process tree is terminated too. This implicitly distinguishes it from the PID-level siblings (process_kill_pid, process_kill_owned_pid), but no sibling is named, so an agent must infer the boundary from the word 'session'.

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?

'Use only when the user wants that long-running task stopped' gives a real usage condition and a soft exclusion. However, it never names an alternative tool (cancel_task, process_kill_pid, process_send_control) or states prerequisites such as needing a live session id from process_list_sessions, so the when-not-to-use side is left to inference.

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

All AiLinkAny tools Inspect

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

Need Help?