Skip to main content
Glama
Sign In
nextcloud-agent

nextcloud-agent

by Knuckles-Team
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Restore trash item

nextcloud_restore_trash_item

Restore a single item from the Nextcloud trash bin to its original location by providing its trash ID.

Instructions

Restore one trash-bin item to its original location.

MOVE /remote.php/dav/trashbin/{user}/trash/{trash_id}

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": {
      "trash_id": "<trash_id>"
    },
    "name": "nextcloud_restore_trash_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
trash_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is supplied. The description adds the useful detail that the item returns to its original location and names the underlying DAV MOVE call, but omits behavior an agent needs: what happens if the original path is gone, or if a file with the same name now exists, and whether the restore fails or overwrites.

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?

Two short lines, front-loaded with the action and outcome, with zero filler. Including the raw MOVE endpoint is compact and adds orienting context rather than noise, though it is only loosely relevant to an agent caller.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (one required param, no output schema, annotations present), so not much is required, but the description still leaves the parameter's provenance and conflict/failure behavior unstated. Adequate as a minimal definition, not complete for an agent deciding whether a restore will succeed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden for the single parameter, yet it says nothing about trash_id: its format, that it is the identifier returned by nextcloud_list_trash, or whether it is path-like or opaque. The DAV path template hints at the value's role but not its construction.

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?

"Restore one trash-bin item to its original location" gives a specific verb (restore), a specific resource (trash-bin item), and the resulting effect (returns to original location). No sibling duplicates this behavior, so it is distinguishable from delete_item, list_trash, and restore_version.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied: the tool applies to an item already in the trash, discovered presumably via nextcloud_list_trash. But the description never states that trash_id must come from list_trash, nor what to do if the tool fails, nor contrasts with restore_version, which is a different restore operation an agent could confuse it with.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools