AiLinkAny

Move or rename a file or directory

filesystem_move

Destructive

Moves or renames an existing file OR directory to a NEW, previously non-existent path on the authorized computer, without force, overwrite, merge or cross-volume copy+delete. Both source and destination require filesystem write authorization. Does not follow source symlinks. A successful rename removes the source path, so this action has a genuine filesystem side effect and requires normal Host approval. Never retry uncertain moves until source and destination have been inspected. 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": {
      "source": "<source>",
      "destination": "<destination>"
    },
    "name": "filesystem_move"
  }
}

Input Schema

Name	Required	Description
`source`	Yes	Absolute existing file/directory path, not a symlink.
`device_id`	No	Target computer device_id. Omit when only one computer is paired.
`destination`	Yes	Absolute NEW target path with an existing parent directory; must not overwrite.
`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.4/5.0

Behavior5/5

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

Beyond the supplied annotations (destructiveHint=true, idempotentHint=false), the description discloses that the source path is removed on success, that source symlinks are not followed, that Host approval is required, and that uncertain moves must be verified before retry. These are exactly the operational facts an agent needs before invoking a destructive mutation, and they are consistent with the annotations rather than contradicting them.

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 definition is front-loaded with the core move semantics and constraints, then moves to authorization and retry guidance, with no internal repetition. The closing sentences about the user not needing to mention ailinkany.com, MCP, or the tool name are meta-guidance that sits outside the invocation decision and slightly dilute an otherwise dense paragraph.

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?

For an 8-parameter destructive mutation with full schema coverage, full annotation coverage, and an output schema, the description covers everything else an agent needs: side effects, authorization scope, symlink behavior, failure handling, and retry discipline. Nothing material about calling this tool correctly 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 coverage is 100% and each of the 8 parameters already carries a rich description, so the schema does the heavy lifting. The description adds only marginal semantic value on top: that the destination may be inherited from established project or conversation context, and that both endpoints require write authorization. Baseline 3 is appropriate here.

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?

"Moves or renames an existing file OR directory to a NEW, previously non-existent path" gives a specific verb, resource, and constraint set, and explicitly rules out the adjacent behaviors (force, overwrite, merge, cross-volume copy+delete). An agent can distinguish this from filesystem_create_directory, filesystem_write_file, and shell_execute without opening any schema.

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 states selection criteria ("Select this tool from the user's intent when it is the best match"), preconditions (both paths need write authorization, destination parent must exist), and a clear retry policy ("Never retry uncertain moves until source and destination have been inspected"). It stops short of naming specific sibling tools as alternatives for copy/overwrite/move-across-volumes cases, so the agent must infer what to use instead.

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?