EXZA Remote

Create home directory

exza_create_home_directory

Create a new directory in a specified managed home area; existing names are rejected. For a one-level Downloads folder use exza_create_downloads_folder. Requires account-bound computer:write OAuth and any prompted local owner approval.

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": {
      "area": "<area>",
      "path": "<path>"
    },
    "name": "exza_create_home_directory"
  }
}

Input Schema

Name	Required	Description	Default
`area`	Yes	Managed home area, one of the allowed values; no arbitrary filesystem roots.
`path`	Yes	Explicit path inside the scope for this tool; no symlink traversal where prohibited.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Adds real behavior beyond the annotations: name collisions are rejected rather than overwritten, and the call may trigger an interactive owner-approval prompt plus a specific OAuth scope. That complements idempotentHint=false and destructiveHint=false well. It does not say what the call returns or what happens to the path's parent directories.

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

Conciseness5/5

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

Three short clauses, front-loaded with the action and scope, then the sibling routing, then the prerequisites. No filler or redundant restatement of the tool name.

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?

Complete enough for a two-parameter create tool: scope, failure mode, prerequisites, and sibling routing are all present, and annotations cover the safety profile. Only the absence of any statement about the response (no output schema exists) keeps it below 5.

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 the schema already documents the enum constraint on 'area' and the no-symlink rule on 'path'. The description's 'managed home area' phrasing reinforces scope but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 ('Create a new directory') plus the scope ('specified managed home area') and a defining constraint ('existing names are rejected'). It also names the sibling exza_create_downloads_folder and the case that selects it, so an agent can route without opening either 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?

Explicitly routes the one-level Downloads case to exza_create_downloads_folder, and states the prerequisites (account-bound computer:write OAuth, local owner approval). It does not address the other similar sibling exza_create_commander_directory, leaving that comparison to inference.

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

All EXZA Remote 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?