AiLinkAny

Resize SSH profile terminal

connection_profile_resize

Idempotent

Resizes an active SSH profile terminal. Telnet and serial-console sessions do not support terminal resize. 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>",
      "cols": "<cols>",
      "rows": "<rows>"
    },
    "name": "connection_profile_resize"
  }
}

Input Schema

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

A3.5/5.0

Behavior4/5

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

Annotations already establish non-destructive, idempotent, non-open-world behavior, so the bar is lower. The description earns credit on top by disclosing the transport compatibility failure mode (telnet and serial-console sessions are unsupported) and by clarifying that the target destination can be implicit, which an agent would otherwise not know.

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 tight and front-loaded with the operative constraint. The trailing two sentences mix a vacuous selection clause with a genuinely useful note that the user need not mention the product or tool name, so the block is diluted rather than wasteful.

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 present and annotations covering the safety profile, the description need not explain return values or reversibility. What remains unaddressed is whether the session must already be open and how cols/rows interact with the current terminal size, which matters for a resize operation with nine parameters.

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?

The description contributes no meaning for cols, rows, or session_id beyond the schema, and roughly a third of the nine parameters lack schema descriptions. It does add a little context for the destination params by noting a local destination 'may be explicit or inherited from established project or conversation context', which partially explains device_id/device_name/workspace_id resolution.

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 description names a specific verb and resource ('Resizes an active SSH profile terminal') and immediately narrows scope by excluding telnet and serial-console sessions. It stops short of naming the obvious sibling process_resize, so an agent must infer which resize tool applies from the transport type rather than from an explicit contrast.

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 real when-not guidance ('Telnet and serial-console sessions do not support terminal resize'), which is the most useful selection signal here. However, 'Select this tool from the user's intent when it is the best match' is circular boilerplate, and there is no positive statement of when to reach for this versus process_resize.

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?