EXZA Remote

Move home file

exza_move_home_file

Destructive

Move/rename one file within a managed home area without overwrite. Unlike exza_copy_home_file, the object disappears from its source path. 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_move_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.2/5.0

Behavior4/5

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

Annotations already flag destructiveHint=true and non-idempotency, but the description adds real value beyond them: no-overwrite policy on the destination, source removal, the computer:write OAuth scope, and that a local owner approval may be prompted. It leaves unstated whether a move can cross areas or what happens to the destination on failure.

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 short sentences, zero filler: action and constraint first, sibling differentiation second, prerequisites last. Each sentence carries distinct information.

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 destructive, non-idempotent mutation with no output schema, the description covers the essentials an agent needs: no overwrite, source removal, auth scope and approval prompts. The remaining gap is whether 'from' and 'to' must live in the same area and what the tool returns on success.

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 the 'area', 'from' and 'to' semantics are already documented in the schema, including the allowed enum values and the overwrite refusal. The description repeats the no-overwrite rule and the single-file constraint but adds no path syntax or cross-area guidance, so 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+resource ('Move/rename one file within a managed home area') and immediately contrasts with the sibling exza_copy_home_file, so an agent can separate the two without reading 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?

Explicitly names the alternative (exza_copy_home_file) and the discriminator: the object disappears from its source path. It does not cover other nearby options such as exza_trash_home_file for deletion or say when a move should be refused outright, so exclusions are only partial.

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?