EXZA Remote

Trash home file

exza_trash_home_file

Destructive

Move one selected managed-home file or folder to EXZA private recycle bin (recoverable deletion); it disappears from its original location. Restore with exza_restore_home_file. 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>",
      "path": "<path>"
    },
    "name": "exza_trash_home_file"
  }
}

Input Schema

Name	Required	Description	Default
`area`	Yes	Managed home area, one of the allowed values; no arbitrary filesystem roots.
`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.3/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, but the description adds the crucial nuance that this is a recycle-bin move rather than permanent removal, plus the required computer:write OAuth scope and possible local owner approval. It leaves out edge behavior such as what happens when the path does not exist.

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, each carrying distinct information: what happens, how to undo it, and what authorization is needed. The effect is front-loaded with no filler.

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 two-parameter mutation tool with no output schema, the description covers the action, its recoverability, the inverse tool, and the auth prerequisites. An agent has everything needed to call it correctly and warn the user appropriately.

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 both parameters are already documented with enum and path constraints. The description only reinforces that a single item is moved ('one selected'), which is marginal added meaning; 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 ('Move one selected managed-home file or folder to EXZA private recycle bin') plus the observable effect ('disappears from its original location'), which cleanly separates it from siblings like exza_move_home_file and exza_list_home_trash.

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?

Names the inverse operation explicitly ('Restore with exza_restore_home_file') and frames the tool as recoverable deletion, which gives clear context for when to choose it. It does not explicitly contrast against exza_move_home_file, so the when-not guidance is incomplete.

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?