Skip to main content
Glama
wiktorekdev

nuvio-mcp

by wiktorekdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Reorder collections

nuvio_reorder_collections

Reorder collections by providing every collection ID exactly once in the desired order. Preview changes with a dry run and snapshot the previous state, so you can revert with undo.

Instructions

Set collection order. Provide every collection id 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
ordered_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

A3.8/5.0
Behavior4/5

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

Annotations already signal a mutating, non-idempotent operation, and the description adds genuinely useful context: a snapshot is taken before the write and the change can be reverted with nuvio_undo. It also mentions dry_run support without contradicting the annotations or the schema.

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 with no filler: the first states the action, the second defines the critical parameter contract, and the third communicates safety behavior. Every clause earns its place.

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 small, three-parameter write operation, the description covers the required parameter semantics, the dry-run preview path, and the rollback mechanism. The main gaps are the unaddressed profile_id parameter and the lack of explicit guidance about when this tool applies versus the other reorder tools.

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?

For ordered_ids, the description adds crucial meaning beyond the schema: every collection id must appear exactly once and the order is the desired final order. However, profile_id is not described at all, and dry_run is described more fully in the schema than in the tool description. With only 33% schema description coverage, this only partially compensates.

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?

'Set collection order' clearly names the verb and resource, and 'Provide every collection id exactly once' adds important scope by indicating this is a full-order replacement rather than a partial move. It is clear enough to distinguish from the addon/plugin/folder reorder siblings by noun, but it does not explicitly call out those siblings.

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 description gives operational context—how to supply the ordered ids and that dry_run/undo are available—but it never states when to choose this tool over nuvio_reorder_collection_folders, nuvio_reorder_addons, or nuvio_reorder_plugins. Usage guidance is mostly implied by the resource noun and the instruction to provide every collection id exactly once.

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