AiLinkAny

Open saved SSH, Telnet, or serial connection

connection_profile_open

Opens a locally saved SSH, Telnet, or serial-console profile and returns an opaque session_id. Authentication secrets are read only by the Windows client from local secure storage and are never sent through MCP. Use the profile id or exact profile name returned by connection_profile_list. SSH Host Key must already be trusted locally before AI-driven SSH connection. Telnet is plaintext and should only be used when the locally configured profile explicitly uses Telnet. 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": {
      "profile": "<profile>"
    },
    "name": "connection_profile_open"
  }
}

Input Schema

Name	Required	Description
`cols`	No	SSH terminal columns. Defaults to 120.
`rows`	No	SSH terminal rows. Defaults to 30.
`profile`	Yes	Local connection profile id or exact profile name.
`device_id`	No	Target computer device_id. Omit when only one computer is paired.
`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

A4.1/5.0

Behavior4/5

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

Goes well beyond the annotations by disclosing the credential model (secrets read only by the Windows client from local secure storage, never sent through MCP), the returned session_id, and the plaintext risk of Telnet. annotations already flag openWorldHint=true and destructiveHint=false. The gap is session lifecycle: with idempotentHint=false, the description never says whether calling twice spawns a second session or whether the session must be closed.

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

Conciseness4/5

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

The core action, return value, and credential model are front-loaded in the first two sentences, and the security caveats follow logically. The tail about not needing to mention ailinkany.com, MCP, or the tool name is meta-guidance that dilutes a technical definition, though it does serve a routing purpose.

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 and parameter coverage is complete, so the description only needs to carry purpose, prerequisites, and risk — which it does in detail. The one omission an agent would want is what happens after open: session lifetime, and which sibling continues the interaction.

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%, so all nine parameters are already documented in the schema, and the description's only parameter guidance ('profile id or exact profile name returned by connection_profile_list') restates the schema text. It adds no meaning for rows/cols, device_id/device_name, retry_token, or the workflow/workspace/session ids, so the baseline 3 applies.

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 (opens) plus the resource (a locally saved SSH/Telnet/serial-console profile) and names the concrete result (an opaque session_id). The mention of connection_profile_list for obtaining the profile id also separates it from the list/close/write siblings without requiring a schema read.

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 real prerequisites ('SSH Host Key must already be trusted locally') and a conditional restriction for Telnet ('only when the locally configured profile explicitly uses Telnet'), plus the intent-matching routing hint. What is missing is an explicit handoff to siblings for the next step — it never says to use connection_profile_write to send input or connection_profile_close to end the session.

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?