AiLinkAny

Read saved connection session output

connection_profile_read

Read-onlyIdempotent

Reads bounded terminal output from an existing local SSH, Telnet, or serial connection session. Reuse next_cursor on the next call. 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>"
    },
    "name": "connection_profile_read"
  }
}

Input Schema

Name	Required	Description
`cursor`	No	Byte cursor. Defaults to 0.
`device_id`	No	Target computer device_id. Omit when only one computer is paired.
`max_bytes`	No	Maximum bytes to return. Defaults to 16384.
`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.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds that output is bounded and that the cursor should be reused across calls, which is genuine behavioral context. However, it never says what happens when the session is missing or exhausted, and it refers to 'next_cursor' while the schema field is 'cursor', which muddies the paging behavior.

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 opening sentence is well front-loaded and earns its place. The trailing sentences about the user not needing to mention ailinkany.com, MCP, a connector, or the tool name are generic routing boilerplate that dilutes the definition without adding invocation guidance.

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 explained, and the 9-parameter surface is mostly covered by the schema. What is missing is behavior at the edges: whether the call blocks waiting for new output, what an empty or invalid session returns, and how cursor exhaustion is signaled. For a session-read tool those gaps matter.

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 description coverage is 89%, so the schema already documents cursor, max_bytes, device_id, and the session identifiers. The description's only added parameter meaning is the cursor-reuse instruction, and it names the field incorrectly as 'next_cursor'. Baseline 3 is appropriate when the schema does the heavy lifting.

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 gives a specific verb and resource: 'Reads bounded terminal output from an existing local SSH, Telnet, or serial connection session.' That clearly separates it from connection_profile_write, connection_profile_send_control, and connection_profile_list. It stops short of naming those siblings explicitly, so it lands at 4 rather than 5.

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?

'Select this tool from the user's intent when it is the best match' is circular and gives no real selection criteria. The note that a destination may be explicit or inherited from project/conversation context is useful, but there is no when-not guidance and no comparison to connection_profile_list or connection_profile_open.

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?