Skip to main content
Glama
wiktorekdev

nuvio-mcp

by wiktorekdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Install a plugin

nuvio_add_plugin

Install a plugin on a Nuvio profile by URL while preserving the existing plugin list. Preview changes with dry_run or revert to the pre-install state using undo.

Instructions

Install a plugin on a profile by URL, preserving the existing plugin list. Supports dry_run and snapshots the previous state before the write; revert with nuvio_undo.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
nameNo
dry_runNoReturn the diff without writing anything (no snapshot, no audit entry).
enabledNo
repo_typeNo
profile_idNo

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?

Beyond the annotations, the description discloses important behaviors: it is additive ('preserving the existing plugin list'), supports dry runs, snapshots the previous state before the write, and provides a revert path via nuvio_undo. This meaningfully augments the sparse annotation set and helps agents understand side effects.

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 dense sentences contain all core information with no filler. The primary action is front-loaded, and the behavioral notes (dry run, snapshot, undo) are placed in a single follow-up sentence.

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 main action and safety semantics well, but with 6 parameters, no output schema, and no usage alternatives, it leaves meaningful gaps: parameter meanings for name/enabled/repo_type and guidance on when to use related sibling tools are missing.

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 17%, so the description should compensate, but it only clarifies 'url' (the plugin source) and 'dry_run' implicitly. Parameters such as name, enabled, repo_type, and profile_id receive no semantic explanation beyond basic names, leaving agents to guess at their formats and roles.

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 a specific verb and resource ('Install a plugin on a profile by URL') and adds the key scope 'preserving the existing plugin list.' This clearly distinguishes it from related plugin management siblings like nuvio_update_plugin, nuvio_remove_plugin, and nuvio_reorder_plugins.

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 when to use the tool: adding a plugin to a profile via URL without replacing the current list. However, it offers no explicit guidance on alternatives or exclusions, such as when to use nuvio_update_plugin instead, nor does it mention prerequisites like profile existence or valid URL sources.

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