Skip to main content
Glama
Sign In

AiLinkAny

by io.github.zhangduochuan
OverviewDiscussionsAdmin

Send PTY control signal

process_send_control
Destructive

Sends a terminal control input to a running PTY session. ctrl_c uses terminal input semantics rather than force-killing the process tree. ctrl_break is accepted by the protocol but may return a platform-not-supported error when the client cannot provide true Ctrl+Break semantics. 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>",
      "control": "<control>"
    },
    "name": "process_send_control"
  }
}

Input Schema

NameRequiredDescriptionDefault
controlYes
device_idNoTarget computer device_id. Omit when only one computer is paired.
session_idYes
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

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds real behavioral context beyond them: ctrl_c goes through terminal input semantics rather than tearing down the process tree, and ctrl_break may fail with a platform-not-supported error. It still leaves open whether the session survives, whether state is lost, or what a success result looks like, so it is not fully transparent.

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 two sentences are dense and front-loaded with the useful semantics. The trailing sentences about selecting from user intent, inherited context, and not needing to mention ailinkany.com/MCP/the tool name are generic connector boilerplate that does not help an agent decide how to invoke this specific tool.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. What remains thin is the interaction between the optional scoping parameters (workflow_id, ai_session_id, workspace_id) and a control signal, but for a two-required-parameter signal tool the description is otherwise sufficient.

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?

With 75% schema description coverage across 8 parameters, the schema already carries most semantics; the description's main contribution is explaining the control enum values, which the schema lists without description. The device_id/device_name and session-context parameters get only a passing nod ("a local destination may be explicit or inherited") and retry_token/workflow_id are not addressed at all.

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?

The description gives a specific verb and resource ("Sends a terminal control input to a running PTY session") and then defines each of the two accepted control values, so the agent knows exactly what the tool does. It also contrasts ctrl_c with force-killing the process tree, which separates it from the kill/stop siblings without needing to open their schemas.

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?

There is an implicit usage rule (prefer ctrl_c over force-killing when the goal is a terminal-style interrupt), plus routing notes about destination being explicit or inherited from context. But it never states when to pick process_kill_pid, process_kill_owned_pid, process_stop, or process_write_stdin instead, and gives no prerequisites or exclusions.

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