Skip to main content
Glama
wiktorekdev

nuvio-mcp

by wiktorekdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Remove an addon

nuvio_remove_addon
Destructive

Remove an addon from a Nuvio profile. Use dry_run to preview the change; a snapshot is saved so you can undo if needed.

Instructions

Uninstall one addon 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. Changed4 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"
+}
    • removedInput schema / properties / url / format
      Removed value: -"uri"
    • addedInput schema / properties / url / minLength
      Added value: +1
  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 declare destructiveHint=true and readOnlyHint=false. The description adds value by disclosing dry_run support, snapshot-before-write behavior, and the revert path via nuvio_undo. This provides concrete operational context beyond the annotations without contradicting them.

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 with no wasted words. The primary purpose is front-loaded, followed by essential behavioral notes (dry_run, snapshot, revert). This is concise and well-structured.

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 action and safety features (dry_run, snapshot, revert), but omits the confirm requirement (though present in schema), the ambiguity between id and url, and the default profile_id. Since there is no output schema, return values are not needed. For a destructive tool, more guidance on identifiers and confirmation would improve completeness.

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% (confirm and dry_run have descriptions). The description only mentions dry_run, leaving id, url, and profile_id unexplained. It does not clarify which identifier is required or the default profile_id, failing to compensate for the low schema 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 states 'Uninstall one addon from a profile' with a clear verb (uninstall) and resource (addon from a profile). This distinguishes it from siblings like nuvio_add_addon and nuvio_toggle_addon by specifying removal of a single addon. The purpose is unambiguous.

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 does not explicitly state when to use this tool versus alternatives such as nuvio_toggle_addon (for temporary disable) or nuvio_remove_plugin (for plugins). It mentions revert with nuvio_undo, which implies a recovery path, but lacks explicit selection criteria or exclusions. The usage is implied by the name and purpose, not articulated.

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