AiLinkAny

Send message to local coding agent

agent_send

Destructive

Sends a prompt or follow-up to an existing local coding Agent through its current PTY. Reuse the same agent_id for follow-ups; do not start a second Agent merely to continue the same task. 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>",
      "message": "<message>"
    },
    "name": "agent_send"
  }
}

Input Schema

Name	Required	Description
`message`	Yes	Prompt or follow-up message to send to the existing Agent.
`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

A4/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is partly carried by structured fields. The description adds useful context that the message is injected into an existing PTY session (implying the agent must already be running), but it never warns about irreversibility, permission needs, or what happens if the agent is idle or busy.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core behavior and the follow-up/continuity rule are front-loaded in the first two sentences, which is efficient. The trailing sentences about selecting by user intent and the user not needing to mention ailinkany.com or MCP are somewhat meta and padding-like, though they do serve tool-selection purposes.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With eight parameters, full schema coverage, an output schema and populated annotations, the description covers the remaining gaps an agent needs: which id to reuse, that the PTY must already exist, and how the destination is resolved. Nothing critical for correct invocation is missing.

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 parameter including retry_token, device_name and ai_session_id is already documented in the schema. The description adds only a light layer of meaning about choosing an existing agent_id versus creating one and about inheriting a local destination from context, which does not meaningfully exceed the schema.

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 description opens with a specific verb and resource: "Sends a prompt or follow-up to an existing local coding Agent through its current PTY." It also distinguishes the tool from agent_start by insisting on reusing the same agent_id rather than starting a second Agent, so an agent can route correctly among the siblings.

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 clear usage context: reuse agent_id for follow-ups, don't start a new Agent for the same task, and the destination may be explicit or inherited from project/conversation context. It stops short of naming alternatives such as agent_send_peer for remote peers or agent_resume for stopped agents, so the routing guidance is strong but not exhaustive.

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?