EXZA Remote

Copy commander file

exza_copy_commander_file

Create a copy of one owner-authorized file up to 8 MB without overwriting. The source remains; use exza_move_commander_file when moving instead. 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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "exza_copy_commander_file"
  }
}

Input Schema

Name	Required	Description	Default
`to`	Yes	New destination path; overwrites are refused where described.
`from`	Yes	Existing source path; must be in the authorized scope.

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?

Annotations already declare the write/safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), and the description still adds real context: an 8 MB size ceiling, destination overwrites being refused, the source being preserved, and a computer:write OAuth plus local owner-approval requirement. It stops short of saying what the caller receives or what error surfaces on an overwrite attempt.

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 tight sentences with no filler: the operation and its limits lead, the alternative routing follows, and prerequisites close. Every clause earns its place and nothing is repeated from the schema.

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 two-parameter, non-destructive copy with full annotation coverage, the description supplies the size cap, overwrite policy, retention of the source, and auth requirements. The one remaining hole is outcome disclosure, since there is no output schema to explain what a successful or refused copy returns.

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 description coverage is 100%, with both from and to already documented as source path and destination path, so the schema carries the heavy lifting. The description adds only indirect meaning (authorized-scope, no-overwrite destination) and never names either parameter, so baseline 3 is appropriate.

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 a copy of one owner-authorized file" gives a specific verb plus resource, and the 8 MB cap and no-overwrite rule define scope precisely. It also distinguishes itself from the move sibling in the same sentence, so an agent can tell the two apart 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?

It explicitly names exza_move_commander_file as the alternative when the source should not remain, which is a clear use-vs-use routing rule. It does not address the nearest namespace-twin, exza_copy_home_file, so the agent still has to infer commander-scope versus home-scope selection.

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?