Skip to main content
Glama
wiktorekdev

nuvio-mcp

by wiktorekdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Remove a collection folder

nuvio_remove_collection_folder
Destructive

Delete a folder from a collection, with dry-run preview and automatic snapshot for undo via nuvio_undo.

Instructions

Remove a folder from a collection. Supports dry_run and snapshots the previous state before the write; revert with nuvio_undo.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoRequired to actually apply a destructive change. Without it a preview is returned.
dry_runNoReturn the diff without writing anything (no snapshot, no audit entry).
folder_idYes
profile_idNo
collection_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.1
    • changedInput schema / properties / confirm / description
      Previous value: -"Required for reversible destructive changes. Without it a preview is returned."New value: +"Required to actually apply a destructive change. Without it a preview is returned."
    • 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

B3.3/5.0
Behavior4/5

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

The description discloses that the operation snapshots the previous state and can be reverted with nuvio_undo, which adds context beyond the annotations (destructiveHint=true, readOnlyHint=false). It does not contradict annotations; it confirms the destructive nature and adds dry_run capability. However, it does not mention the confirm requirement, which is a notable behavioral omission.

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?

The description is a single sentence plus a short clause, with the core action front-loaded and no wasted words. It is concise and well-structured.

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?

For a destructive tool with 5 parameters, no output schema, and a confirm gate, this description is far from complete. It omits the crucial confirm requirement, doesn't explain what the parameters mean, and gives no indication of the response format. An agent would likely invoke it incorrectly without reading the schema, and even then, the undocumented parameters remain ambiguous.

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

Parameters1/5

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

With only 40% schema coverage, the description carries a heavy burden to explain parameters, but it says nothing about folder_id, collection_id, profile_id, confirm, or dry_run. The schema descriptions for confirm and dry_run exist, but the other three parameters are undocumented in both schema and description. This is a severe gap.

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 clearly states the verb 'remove' and the resource 'a folder from a collection', distinguishing it from sibling operations like add, update, or reorder. It is not a tautology; it adds the scope 'from a collection' and mentions supporting behaviors.

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?

The description provides no guidance on when to choose this tool over alternatives like nuvio_update_collection_folder or nuvio_delete_collection. It mentions dry_run and revert via nuvio_undo, but does not explicitly state conditions or exclusions. Critical usage context like the need for confirm to actually apply destructive changes is left entirely to the schema.

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