EXZA Remote

Create downloads folder

exza_create_downloads_folder

Create one new direct subfolder of macOS Downloads. No file writes or overwrites; for nested folders or other managed areas use exza_create_home_directory. 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": {
      "name": "<name>"
    },
    "name": "exza_create_downloads_folder"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Exact selected application, window or folder name; avoid guesses.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 7, 2026
- addedInput schema / properties / name / description
```
Added value: +"Exact selected application, window or folder name; avoid guesses."
```
First observedNov 7, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Beyond the annotations, it adds two pieces of real behavioral context: no file writes/overwrites occur, and the call requires a specific OAuth scope plus possibly prompted local owner approval. The annotations already declare destructiveHint=false and readOnlyHint=false, which the description is consistent with. It does not say what happens if a folder of that name already exists (idempotentHint=false), which is the one notable 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?

Two tight sentences: the positive scope comes first, the alternative second, and the auth requirement last. Nothing is redundant and nothing is buried.

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 single-parameter, non-destructive create with no output schema, the description covers scope, alternative, and prerequisites adequately. The remaining omission is behavior on a pre-existing folder name, which matters given idempotentHint=false.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the schema's param text is generic boilerplate ("application, window or folder name") while the description narrows the meaning to exactly one direct subfolder name under Downloads. That constraint adds genuine meaning; it stops short of stating allowed characters or duplicate-name handling.

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?

"Create one new direct subfolder of macOS Downloads" gives a specific verb, resource, and a hard scope limit (one, direct subfolder). It is immediately distinguishable from exza_create_home_directory, which is named as the tool for other locations.

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?

The description explicitly routes the agent: use this only for direct subfolders of Downloads, and use exza_create_home_directory for nested folders or other managed areas. It also states the prerequisite (account-bound computer:write OAuth plus local owner approval), so the agent knows the call may block on consent.

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?