Skip to main content
Glama
wiktorekdev

nuvio-mcp

by wiktorekdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Duplicate a collection

nuvio_duplicate_collection

Duplicate a collection, including folders and catalog sources, under a new ID placed after the source. Preview changes with dry run; snapshots enable undo.

Instructions

Copy a collection (including folders and catalog sources) under a new id, placed right after the source. Supports dry_run and snapshots the previous state before the write; revert with nuvio_undo.

Input Schema

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

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 indicate a non-read-only, non-destructive write. The description adds that dry_run is supported, that a snapshot of the previous state is taken before the write, and that nuvio_undo can revert. It also notes the copy's placement. This is meaningful behavioral context beyond the annotations, though it doesn't cover all edge cases.

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?

Two sentences, front-loaded with the purpose, then a compact statement of side effects and recovery. No redundant or extraneous content.

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 description covers the core behavior and safety net, but omits return behavior (no output schema) and leaves new_title/profile_id semantics unstated. For a 5-parameter tool with no output schema, this is moderately complete but not fully.

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 only 20% (dry_run). The description explains collection_id and new_id implicitly, and mentions dry_run, but does not clarify new_title or profile_id. Since the schema itself provides no descriptions for these, the tool description fails to compensate for the low coverage.

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 uses a specific verb ('Copy') and resource ('collection'), with scoping details ('including folders and catalog sources') and placement ('right after the source'). This clearly differentiates it from create/update/delete collection 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 implies usage for duplicating an existing collection, but provides no explicit when-to-use vs alternatives or exclusions. The mention of nuvio_undo is for recovery, not tool selection, so agents are left to infer when this should be chosen over create_collection or other options.

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