EXZA Remote

List external home folder

exza_list_external_home_folder

Read-onlyIdempotent

List at most 200 non-hidden file and folder names in an explicitly approved user-home directory outside the EXZA workspace, without opening contents or retaining permanent home access. Use exza_list_workspace_files for the isolated workspace instead. Requires computer:write OAuth plus native approval, since private names may be exposed even though no files are changed.

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_list_external_home_folder"
  }
}

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.7/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations it discloses the 200-entry cap, that hidden entries are excluded, that contents are not opened, and that permanent home access is not retained. It also names the computer:write OAuth scope and native approval requirement, which matters because a readOnly tool still exposes private names — the scope name is a permission label, not a contradiction of readOnlyHint.

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 compact sentences, front-loaded with capability and limit, then the alternative, then the auth prerequisite. No filler and no repetition of the schema or annotations.

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 a single-parameter read tool with no output schema, it covers scope, result limit, filtering, privacy exposure, approval flow, and the sibling alternative. An agent has everything needed to decide and invoke correctly.

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 description adds real meaning: path must point inside an explicitly approved user-home directory outside the EXZA workspace. That constraint is not derivable from the schema's generic "inside the scope for this tool" 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?

"List at most 200 non-hidden file and folder names" gives a specific verb, resource, and a hard result bound, plus the scope (an approved user-home directory outside the EXZA workspace). It explicitly contrasts with exza_list_workspace_files, so the agent can separate the two 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?

Clear when-to-use framing: only for explicitly approved home directories outside the workspace, and it routes workspace listing to exza_list_workspace_files. It does not distinguish itself from other home-directory siblings such as exza_list_home_files or exza_search_home_files, which is the main gap.

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?