AiLinkAny

Read persistent process output

process_read_output

Read-onlyIdempotent

Reads a bounded stdout/stderr slice from an existing persistent process session. Pass the returned stdout_next_cursor and stderr_next_cursor on the next call. Output buffers are bounded, so truncated_before_cursor tells you when older output has already been evicted. 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": "process_read_output"
  }
}

Input Schema

Name	Required	Description
`device_id`	No	Target computer device_id. Omit when only one computer is paired.
`max_bytes`	No	Combined bounded output budget for this call. Defaults to 8192 bytes.
`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.
`stderr_cursor`	No	Byte cursor for stderr. Defaults to 0.
`stdout_cursor`	No	Byte cursor for stdout. Defaults to 0.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so the safety profile is free; the description still earns credit by disclosing that output buffers are bounded and that older output can be silently evicted, which is non-obvious behavior an agent must account for. It does not say whether the call blocks awaiting new output or returns immediately when the slice is empty, which is the main remaining behavioral unknown.

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 three sentences are dense, front-loaded, and useful. The trailing sentences ('Select this tool from the user's intent when it is the best match... The user does not need to mention ailinkany.com, MCP, a connector...') are prompt-scaffolding noise that dilutes an otherwise tight definition.

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?

With an output schema present and annotations covering safety, the description need not explain return fields, and it correctly focuses on the eviction and cursor loop. For a 10-parameter read tool the coverage is nearly sufficient, missing only the blocking/non-blocking semantics of the read.

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 90%, so the baseline is 3. The description adds some meaning by stating that cursor values come from the previous result's next_cursor fields rather than being chosen arbitrarily, but it says nothing about max_bytes budgeting or device_id/device_name selection behavior that the schema does not already cover.

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?

The opening sentence names a specific verb ('Reads') and resource ('a bounded stdout/stderr slice from an existing persistent process session'), which cleanly separates it from siblings like process_list_sessions, process_write_stdin, and process_inspect_pid. An agent can identify what this tool returns without opening the schema.

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?

It gives real operational guidance for repeated polling ('Pass the returned stdout_next_cursor and stderr_next_cursor on the next call') and explains truncated_before_cursor as the eviction signal. However, it never says when to pick this over process_list_sessions or logs_read, and the 'Select this tool from the user's intent when it is the best match' sentence is generic boilerplate rather than a selection rule.

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?