AiLinkAny

Resize interactive PTY

process_resize

Idempotent

Resizes a running PTY process session. Use this after process_start with pty=true when a terminal-aware program needs updated rows and columns. 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": "process_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.7/5.0

Behavior3/5

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

Annotations already declare idempotentHint=true, destructiveHint=false, and readOnlyHint=false, so the safety profile is covered. The description adds useful context that the target must be a running PTY session created via process_start, but says nothing about failure behavior for non-PTY or terminated sessions, nor whether the resize is reflected to the attached program immediately.

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 efficient and front-load the important trigger. The remaining two sentences ('Select this tool from the user's intent when it is the best match...' and the note about not needing to mention ailinkany.com/MCP) are generic boilerplate that adds no selection or invocation value and dilutes the definition.

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?

An output schema exists, so return values need not be described, and the annotations cover safety. However, for a mutation tool with nine parameters, the description leaves the multi-device routing and retry semantics largely to the schema and does not state what happens when the session is not PTY-capable, which is the main invocation risk.

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 67%, and the description only reinforces the rows/columns concept already obvious from the required 'cols' and 'rows' parameters. It gestures at destination selection ('explicit or inherited from established project or conversation context') but does not clarify when to pass device_id versus device_name, or what retry_token and the session/workflow identifiers do beyond their schema text.

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 and resource: 'Resizes a running PTY process session.' The clause 'Use this after process_start with pty=true' further disambiguates it from siblings like process_start, process_send_control, and connection_profile_resize, which operate on different objects.

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 a clear trigger condition: after process_start with pty=true, when a terminal-aware program needs updated rows and columns. It does not name a specific alternative tool to use instead when the session is not a PTY, but the prerequisite framing is strong enough to select correctly in most cases.

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?