Skip to main content
Glama
Sign In

AiLinkAny

by io.github.zhangduochuan
OverviewDiscussionsAdmin

Terminate a PID owned by this account's active process session

process_kill_owned_pid
Destructive

Terminate only an explicitly selected PID from the same user's and device's active persistent process_start session. Requires the exact session_id AND PID; denies arbitrary Windows PIDs, other users' sessions, stale sessions, the agent process, and mismatched PIDs. Confirms process exit before reporting success. This is a destructive non-idempotent action; never blindly retry when response is uncertain; inspect original session state first. 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>",
      "pid": "<pid>"
    },
    "name": "process_kill_owned_pid"
  }
}

Input Schema

NameRequiredDescriptionDefault
pidYesExact PID returned by that active session; arbitrary OS PID is forbidden.
device_idNoTarget computer device_id. Omit when only one computer is paired.
session_idYesExact owned process_start session ID, not another user's session.
device_nameNoComputer name or ailinkany.com remark (e.g. home PC). Prefer this when the user names a computer.
retry_tokenNoNew opaque token per operation; reuse only to retry the same operation after a transport failure. No user content.
workflow_idNoOptional workflow id; pass together with ai_session_id.
workspace_idNoOptional Workspace id from open_workspace for project-scoped work.
ai_session_idNoOptional 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

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare destructive=true and idempotent=false, but the description adds substantial operational context: the exact session_id+PID pairing requirement, denial of stale/agent/mismatched PIDs, confirmation of process exit before reporting success, and an explicit warning not to blindly retry after an uncertain response. That is exactly the extra guidance a destructive operation needs.

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 three sentences are dense and front-loaded with the critical constraints. However, the sentence 'A local destination may be explicit or inherited from established project or conversation context' is off-topic boilerplate for a PID-termination tool, and the closing sentence about not needing to mention ailinkany.com/MCP is generic padding.

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?

With an output schema present, return values need no explanation, and the description still notes that exit is confirmed before success is reported. For a destructive, non-idempotent 8-parameter tool with full schema coverage, the remaining gap is minor: retry_token reuse semantics are only in the schema, not reinforced in prose.

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 description coverage is 100%, so all 8 parameters (device_id, retry_token, workflow_id, workspace_id, ai_session_id, etc.) are already documented. The description reinforces that both session_id and PID must be exact, but adds no syntax or format detail beyond the schema, which is the expected baseline.

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 with scope: 'Terminate only an explicitly selected PID from the same user's and device's active persistent process_start session.' It also implicitly separates itself from process_kill_pid/process_stop by denying 'arbitrary Windows PIDs' and requiring an owned session, so an agent can distinguish it from siblings without opening schemas.

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 clear positive conditions (best match for user intent, session may be explicit or inherited from context) and explicit exclusions (other users' sessions, stale sessions, agent process, mismatched PIDs). It never names the sibling tool the agent should use instead for non-owned PIDs, so routing is inferred rather than spelled out.

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

All AiLinkAny 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