EXZA Remote

Copy home file

exza_copy_home_file

Make a new copy in the same managed home area without overwriting. For a general owner-approved path use exza_copy_commander_file; do not use exza_move_home_file when the original must remain. 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": {
      "area": "<area>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "exza_copy_home_file"
  }
}

Input Schema

Name	Required	Description
`to`	Yes	New destination path; overwrites are refused where described.
`area`	Yes	Managed home area, one of the allowed values; no arbitrary filesystem roots.
`from`	Yes	Existing source path; must be in the authorized scope.

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?

Annotations already declare destructiveHint=false and readOnlyHint=false, and the description's no-overwrite claim is consistent with that. It adds genuinely non-obvious behavior beyond the annotations: the account-bound computer:write OAuth requirement and the possibility of a prompted local owner approval. It stops short of saying what happens on a destination collision or what the return payload contains, which keeps it from a 5.

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?

Three tight sentences, with the core action and non-overwrite constraint front-loaded, then routing to alternatives, then prerequisites. No filler, though the third sentence's two prerequisites could be compressed slightly.

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-parameter mutation with no output schema, the description covers scope, non-overwrite guarantee, sibling routing, and authorization prerequisites. The main residual gap is the result of the operation — whether it returns the new path or just a success status — which an agent may want for chaining follow-up calls.

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%, so all three parameters (area, from, to) are already documented in the schema, including the enum constraint on area and the overwrite refusal. The description only reinforces the managed-home scope concept, adding little beyond what the structured fields provide, so the baseline 3 applies.

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 ("Make a new copy") bound to a specific scope ("in the same managed home area") plus a key constraint ("without overwriting"). It also explicitly contrasts itself with exza_copy_commander_file, so an agent can separate it from the general-purpose copy sibling 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 Guidelines5/5

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

Names both the positive alternative (exza_copy_commander_file for a general owner-approved path) and the exclusion (do not use exza_move_home_file when the original must remain). The conditions selecting each tool are stated directly rather than implied.

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?