Skip to main content
Glama
wiktorekdev

nuvio-mcp

by wiktorekdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Remove a plugin

nuvio_remove_plugin
Destructive

Uninstall a plugin from a Nuvio profile. Supports dry-run previews and snapshots the prior state so you can undo changes with nuvio_undo.

Instructions

Uninstall a plugin from a profile. Supports dry_run and snapshots the previous state before the write; revert with nuvio_undo.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
urlNo
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).
profile_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 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"
+}
    • addedInput schema / properties / id
      Added value: +{
+  "format": "uuid",
+  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+  "type": "string"
+}
    • removedInput schema / properties / url / format
      Removed value: -"uri"
    • addedInput schema / properties / url / minLength
      Added value: +1
    • removedInput schema / required
      Removed value: -[
-  "url"
-]
  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?

The description adds meaningful behavior beyond the annotations by disclosing that the tool snapshots the previous state before writing and that the operation can be reverted with nuvio_undo. It also advertises dry_run support. This is valuable context not present in the readOnly/destructive hints, and it does not contradict the annotations.

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 dense sentence that front-loads the core action and then adds the two safety-relevant facts: dry_run support and snapshot/undo behavior. There is no filler or redundant restatement of the title.

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?

For a destructive 5-parameter tool with no output schema, this is adequate but has clear gaps. The removal behavior and safety net are explained, and confirm/dry_run are documented in the schema, but the plugin identity semantics and the expected response/preview content are left to inference. An agent could still be unsure which parameter to supply.

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 40%, with id, url, and profile_id lacking descriptions. The tool description does not clarify whether a plugin is identified by id or url, what happens if both are provided, or how profile_id scopes the operation. Mentioning dry_run adds little since dry_run already has a schema description.

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+resource combination: 'Uninstall a plugin from a profile.' This clearly distinguishes it from sibling tools like nuvio_add_plugin, nuvio_update_plugin, nuvio_toggle_plugin, and nuvio_list_plugins, and it is not just a restatement of the title.

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 a clear operation context and mentions a safe invocation path via dry_run and a recovery path via nuvio_undo. However, it does not explicitly state when to use this tool versus alternatives such as nuvio_toggle_plugin for disabling or nuvio_update_plugin for modifying a plugin. The usage guidance is implied rather than explicit.

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