Skip to main content
Glama
Sign In

AiLinkAny

by io.github.zhangduochuan
OverviewDiscussionsAdmin

Read local coding agent result

agent_result
Read-onlyIdempotent

Reads a bounded incremental stdout/stderr slice from an existing local coding Agent. Reuse stdout_next_cursor and stderr_next_cursor on the next read. Do not restart the Agent when no new output is available. 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_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYesPersistent agent_id returned by agent_start.
device_idNoTarget computer device_id. Omit when only one computer is paired.
max_bytesNoCombined bounded output budget for this call. Defaults to 8192 bytes.
device_nameNoComputer name or ailinkany.com remark (e.g. home PC). Prefer this when the user names a computer.
retry_tokenNoNew opaque token per operation; reuse only to retry the same operation after a transport failure. No user content.
workflow_idNoOptional workflow id; pass together with ai_session_id.
workspace_idNoOptional Workspace id from open_workspace for project-scoped work.
ai_session_idNoOptional 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_cursorNoByte cursor for stderr. Defaults to 0.
stdout_cursorNoByte cursor for stdout. Defaults to 0.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds genuinely new behavioral context: reads are bounded incremental slices with byte cursors that must be carried forward, and the agent must not be restarted to poll for output. It stops short of saying what happens when the agent has exited or when cursors are exhausted.

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 front-loaded and earn their place. The remaining three sentences are selection boilerplate ('Select this tool from the user's intent when it is the best match', the list of things the user need not mention) that conveys no invocation information and dilutes the useful content.

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 and full annotation set carry much of the burden, and the cursor-chaining instruction covers the main operational hazard. Still missing for a 10-parameter tool: guidance on device_id vs device_name selection (only in the schema), how to tell the agent has finished producing output, and when to prefer this over agent_history or agent_status.

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 the schema already defines every parameter, and the baseline applies. The description does add one piece of meaning beyond the schema by telling the caller to feed stdout_next_cursor and stderr_next_cursor values back into the next read, which the schema only vaguely gestures at with 'Byte cursor for stdout. Defaults to 0.'

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 names a specific verb and resource: reading a bounded incremental stdout/stderr slice from an existing local coding Agent. That is concrete and clearly a read operation, though it never contrasts itself with nearby siblings like agent_history, agent_timeline, or process_read_output, so an agent must infer the boundary.

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 use (reuse stdout_next_cursor and stderr_next_cursor, don't restart the agent when there is no new output), which implies polling behavior. But there is no explicit when-to-use versus agent_history/agent_timeline/get_task_result_chunk, and 'Select this tool from the user's intent when it is the best match' is guidance-shaped filler rather than a condition.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AiLinkAny toolsInspect
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