AiLinkAny

Create a new directory

filesystem_create_directory

Creates one NEW directory on the authorized computer. Supports recursive parent creation without overwriting an existing directory. Rejects paths outside configured directory protection and the client's trust root. This changes the filesystem and may partially create parents on an OS error; never blindly retry an uncertain command. 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": {
      "path": "<path>"
    },
    "name": "filesystem_create_directory"
  }
}

Input Schema

Name	Required	Description
`path`	Yes	Absolute path of a NEW directory. Already existing targets are rejected.
`parents`	No	Create missing parent directories recursively; defaults to true.
`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.9/5.0

Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false), it discloses that paths outside the protection root are rejected, that parents may be partially created on an OS error, and that an uncertain command should not be blindly retried. That partial-failure and retry guidance is exactly the kind of context annotations cannot carry; only permission/auth requirements are left unstated.

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 first three sentences are front-loaded and dense with real constraints. The trailing sentences about intent matching and the user not needing to mention ailinkany.com, MCP, or the tool name are generic boilerplate that dilutes an otherwise tight definition.

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?

With an output schema present, return values need no explanation, and the description covers the key risks of a non-idempotent mutation: no overwrite, path rejection, partial parent creation, and retry caution. It does not explain how to choose between device_id and device_name, but the schema handles that.

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 documents path, parents, device_id, device_name, retry_token and the session/workspace ids. The description adds only the notion that the destination may be inherited from context, which is marginal over the schema's own wording.

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?

States a specific verb and resource ('Creates one NEW directory on the authorized computer') and immediately scopes it with 'one NEW' and 'without overwriting an existing directory', which separates it from filesystem_write_file and filesystem_move in the sibling list.

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 intent-matching guidance ('Select this tool from the user's intent when it is the best match') and says the destination may be inherited from project or conversation context, but it never names an alternative tool or a when-not-to-use condition, so the agent must infer the boundary against filesystem_list_directory or filesystem_write_file.

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?