AiLinkAny

Send control input to saved connection

connection_profile_send_control

Destructive

Sends a terminal control input to an active saved connection session. ctrl_c is supported for SSH, Telnet, and serial sessions; ctrl_break may be unsupported by a transport. 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": "connection_profile_send_control"
  }
}

Input Schema

Name	Required	Description
`control`	Yes
`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

B3.1/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the risk profile is known. The description usefully adds that ctrl_break may be unsupported by a transport, but it never explains what ctrl_c actually destroys (the foreground running command) or what happens on an unsupported transport — which is the key behavioral detail an agent needs before touching a live session.

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 lead sentence is well front-loaded, but two of the four sentences are generic routing boilerplate ('when it is the best match', the 'user does not need to mention ailinkany.com, MCP...' line) that consume space without informing the call.

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?

With an output schema and full annotations, the description needn't explain returns or safety. For an 8-parameter destructive session-control tool, though, it should state the required session state and the interrupt semantics; the transport caveat is the only substantive addition.

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 75%, so the schema already documents device_id, device_name, retry_token, and the session ids. The description adds only the meaning of the control values at a transport level, and says nothing about how to choose session_id, or the retry_token reuse rule, which the schema covers itself.

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?

The first sentence names a specific verb and resource: sending a terminal control input to an active saved connection session, which separates it from connection_profile_write (data) and process_send_control (local processes). It never explicitly names those siblings, so an agent must infer the distinction from the word 'saved connection'.

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?

'Select this tool from the user's intent when it is the best match' is circular and gives no when-to-use criteria. The only concrete guidance is transport support for ctrl_c vs ctrl_break; there is no statement about prerequisites (session must be open) or why an agent would pick this over connection_profile_write or process_send_control.

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?