EXZA Remote

Create commander directory

exza_create_commander_directory

Create an empty directory within the owner-authorized commander scope, refusing overwrite. Use exza_create_home_directory for narrowly managed home areas. 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": {
      "path": "<path>"
    },
    "name": "exza_create_commander_directory"
  }
}

Input Schema

Name	Required	Description	Default
`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.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (destructiveHint=false, idempotentHint=false), but the description adds real behavior beyond them: it refuses overwrite, requires account-bound computer:write OAuth, and may trigger a local owner approval prompt. It stops short of saying what happens when the path already exists (error vs. silent no-op), which is the one remaining behavioral gap.

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 sentences, each carrying distinct information: scope, overwrite refusal, sibling alternative, and auth requirements. Nothing is repeated from the title and the scoping constraint is front-loaded.

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 one-parameter, non-readOnly creation tool with annotations but no output schema, the description covers scope, safety, auth, and the alternative tool. The only thing left unstated is the result of the call (returned path/handle or error on existing directory), which is a minor gap.

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 single path parameter is already documented with the no-symlink-traversal constraint, so the schema carries the detail. The description adds only the framing that the path must fall inside the owner-authorized scope, which is useful but marginal beyond the schema text.

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 (Create) and resource (empty directory) plus the exact scope (owner-authorized commander scope) and the non-overwrite behavior. It also names the sibling it should not be confused with (exza_create_home_directory), so an agent can separate it from the home-area tools without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit exclusion rule: for narrowly managed home areas use exza_create_home_directory instead. Combined with the stated commander scope, the agent has a clear condition that selects between this tool and its nearest alternative.

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?