AiLinkAny

Resume or probe local coding agent

agent_resume

Idempotent

Probes whether an existing agent_id is still live in the current desktop client. If live, returns the current snapshot (resume_mode=already_live). After client restart, Native PTY Agents are typically not_resumable; use agent_history and start a new Agent. 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": {
      "agent_id": "<agent_id>"
    },
    "name": "agent_resume"
  }
}

Input Schema

Name	Required	Description
`agent_id`	Yes	Persistent agent_id returned by agent_start.
`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

A3.8/5.0

Behavior4/5

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

Annotations already declare idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety bar is partly covered. The description adds genuinely non-obvious behavior: the liveness probe, the resume_mode=already_live snapshot return, and the post-restart non-resumable condition for Native PTY Agents. It does not say what is returned or raised when the agent is not live, which is the main disclosure gap.

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 core liveness and non-resumable information is front-loaded in the first three sentences and earns its place. The trailing lines about selecting from user intent and the user not needing to mention ailinkany.com, MCP, a connector, or a plugin are generic boilerplate that do not help an agent invoke this specific tool and dilute the payload.

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, so return-value detail is not required, and the description covers both the live and post-restart cases. Combined with annotations and full schema coverage, an agent has enough to call it correctly. The only missing piece is the concrete behavior when the agent_id is not live.

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 100%, so every one of the seven parameters is already documented in the schema; baseline is 3. The description adds only the notion that the local destination may be explicit or inherited from project or conversation context, which lightly clarifies device_id/device_name selection. No additional syntax or constraint meaning is contributed beyond the schema.

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 opens with a specific verb and resource: probing whether an existing agent_id is still live in the current desktop client, and states the success shape (resume_mode=already_live). It routes away from itself in the failure case by naming agent_history and starting a new Agent. It does not, however, distinguish itself from close siblings like agent_status or agent_result, which an agent could plausibly confuse it with.

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?

It gives an explicit when-not-to-use rule: after a client restart Native PTY Agents are typically not_resumable, so use agent_history and start a new Agent instead. It also frames intent-based selection. It stops short of stating the alternative for a live-but-different agent or contrasting with agent_status, which leaves some routing to inference.

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?