Skip to main content
Glama
Sign In
nextcloud-agent

nextcloud-agent

by Knuckles-Team
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Restore version

nextcloud_restore_version

Restore a specific stored version of a file so the current content is saved as a version, letting you roll back files to an earlier state.

Instructions

Restore one stored version of a file; the current content becomes a version.

MOVE /remote.php/dav/versions/{user}/versions/{fileid}/{version_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": {
      "path": "<path>",
      "version_id": "<version_id>"
    },
    "name": "nextcloud_restore_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
version_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.0

TDQS

B3.1/5.0
Behavior4/5

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

The annotations declare readOnlyHint=false and destructiveHint=false, and the description earns its keep by explaining why: the current content is preserved as a version rather than lost. That is exactly the fact an agent needs before authorizing a mutation. It stops short of permissions or failure behavior, and the raw MOVE endpoint line is implementation detail rather than behavioral context.

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?

The core action and its most important side effect are front-loaded in a single tight sentence. The trailing MOVE path is short and arguably useful for debugging, though it is the least agent-relevant part of the description.

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

Completeness2/5

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

This is a two-required-parameter mutation tool with zero schema coverage and no output schema. The description never explains how to obtain or format a version_id, nor what the path is relative to, and it omits any mention of permissions or error conditions. The preservation note is good, but the invocation details are missing.

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 must carry both parameters and it does not. 'path' is only hinted at by the word 'file' (no indication it is relative to the user root, or whether it is a file path vs. folder), and 'version_id' appears only inside the URL template with no hint about its format or that it comes from nextcloud_list_versions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Restore one stored version of a file') and adds the scope that only one version is restored at a time. It is distinguishable from nextcloud_list_versions and nextcloud_restore_trash_item, though it never names those siblings explicitly.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus alternatives, and crucially no instruction to call nextcloud_list_versions first to obtain a version_id. The only implied usage comes from the word 'Restore' itself.

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