Skip to main content
Glama
wiktorekdev

nuvio-mcp

by wiktorekdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Reorder folders in a collection

nuvio_reorder_collection_folders

Reorder folders in a Nuvio collection by supplying every folder ID in the desired order. Preview with dry-run and undo via snapshot.

Instructions

Set folder order. Provide every folder id in the collection exactly once, in the desired order. Supports dry_run and snapshots the previous state before the write; revert with nuvio_undo.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dry_runNoReturn the diff without writing anything (no snapshot, no audit entry).
profile_idNo
collection_idYes
ordered_folder_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.1
    • addedInput schema / properties / dry_run
      Added value: +{
+  "description": "Return the diff without writing anything (no snapshot, no audit entry).",
+  "type": "boolean"
+}
  2. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

The description discloses that the tool snapshots the previous state before writing and can be reverted with nuvio_undo, which goes beyond annotations like readOnlyHint=false and destructiveHint=false. It also notes dry_run support, adding useful behavioral context about side effects and safety.

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 concise sentences front-load the core purpose, then add the key constraint and side-effect information. No redundant or filler content is present.

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 reorder operation with no output schema, the description covers the critical details: the ordering invariant, dry-run support, snapshot creation, and revert path. It leaves profile_id selection to the schema default, which is acceptable given the low complexity.

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 only 25%, so the description must compensate. It adds essential semantics for ordered_folder_ids by requiring every folder id exactly once, but it does not clarify collection_id or profile_id semantics beyond what the schema's names and defaults imply.

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?

The description opens with a specific verb and resource, 'Set folder order,' and adds a precise invariant: every folder id in the collection must be provided exactly once in the desired order. This clearly distinguishes it from sibling tools like nuvio_reorder_collections, nuvio_reorder_addons, and nuvio_reorder_plugins.

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?

The intended use is implied through the phrase 'every folder id in the collection,' but the description does not explicitly state when to choose this tool over alternatives or when not to use it. No mention is made of sibling reorder tools, so the guidance is adequate but indirect.

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