Skip to main content
Glama
Sign In

AiLinkAny

by io.github.zhangduochuan
OverviewDiscussionsAdmin

Stop local coding agent

agent_stop
DestructiveIdempotent

Stops an existing local coding Agent. The desktop runtime first sends Ctrl+C and then falls back to terminating the retained process tree if needed. 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_stop"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYesPersistent agent_id returned by agent_start.
device_idNoTarget computer device_id. Omit when only one computer is paired.
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.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already mark this as destructive, idempotent, and non-read-only, but the description adds useful operational detail: the runtime sends Ctrl+C first and then terminates the retained process tree if needed. That explains what the destructive action actually involves beyond the annotation flags. It still does not mention unsaved work, permissions, or side effects on agent history, so it is strong but not exhaustive.

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 useful, stating purpose and shutdown behavior. The later sentences about selecting by user intent and the user not needing to mention ailinkany.com, MCP, connectors, plugins, or the tool name are generic boilerplate that does not help invoke the tool correctly. It is not bloated, but those sentences reduce structure quality.

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?

For a seven-parameter destructive tool with full schema coverage, rich annotations, and an output schema, the description covers purpose, shutdown mechanism, and destination-context inheritance. It lacks explicit alternative-tool routing, but the schema and annotations already cover most remaining invocation details. Overall it is complete enough for an agent to call safely.

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 parameters like agent_id, device_id, device_name, retry_token, workflow_id, workspace_id, and ai_session_id are already documented in the schema. The description only alludes to a local destination being explicit or inherited from context and does not add parameter-specific meaning. With the schema doing the heavy lifting, the baseline score of 3 is appropriate.

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 states a specific verb and resource: 'Stops an existing local coding Agent.' That is clear enough for an agent to understand the operation. It does not explicitly distinguish this tool from nearby siblings such as agent_resume, cancel_task, or process_stop, so it falls short of the top score.

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 says to select this tool 'from the user's intent when it is the best match' and notes that a local destination may be explicit or inherited from context. However, it does not state when to prefer this over alternatives like agent_resume, cancel_task, or process_stop, nor when not to use it. The guidance is implied but not actionable enough for a 4.

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