EXZA Remote

List commander files

exza_list_commander_files

Read-onlyIdempotent

Page through visible child names in one explicit, owner-authorized directory using offset and limit; this does not open file contents. Use exza_list_home_files for bounded Downloads/Desktop/Documents/Pictures/Music areas, or exza_list_workspace_files for the isolated EXZA workspace. A directory outside those scopes requires the separately approved commander computer scope, and returned names may be private. Requires account-bound computer:write OAuth and any prompted local owner approval.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "exza_list_commander_files"
  }
}

Input Schema

Name	Required	Description
`path`	No	Explicit path inside the scope for this tool; no symlink traversal where prohibited.
`limit`	No	Page length, subject to server-side maximum.
`offset`	No	Pagination or output cursor offset; use returned continuation data.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Goes well beyond the read-only/idempotent annotations by disclosing auth requirements (account-bound computer:write OAuth), possible local owner approval prompts, and that returned names may be private. It stops short of describing pagination termination or page-size limits, which the agent still has to infer from the parameters.

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?

Front-loaded with the action and its key exclusion, then routing, then auth. The final sentence packs auth, approval, and privacy into one clause, making it dense but not padded; no sentence is wasted.

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 three-optional-parameter listing tool with no output schema, it covers scope, safety, auth, and return-value sensitivity. The only gap is not saying what the response looks like (whether names come with a continuation token), though the schema hint about continuation data partly covers 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 coverage is 100%, so all three parameters are already documented. The description only adds that path must be an explicit directory inside the authorized scope and that offset/limit drive paging, which is a mild restatement of the schema rather than new syntax or constraint detail.

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 ("Page through visible child names in one explicit, owner-authorized directory") plus the key negative bound ("does not open file contents"), which lets an agent distinguish it from exza_get_commander_file_info or exza_read_workspace_file 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?

Names two concrete alternatives (exza_list_home_files for the bounded user folders, exza_list_workspace_files for the isolated workspace) and states the condition under which this tool is the right one, including the escalation path via the approved commander computer scope.

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?