Skip to main content
Glama
wiktorekdev

nuvio-mcp

by wiktorekdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Install an addon

nuvio_add_addon

Install an addon on a Nuvio profile from a manifest URL, preserving the current addon list. Preview changes with dry-run and revert safely via snapshot before writing.

Instructions

Install an addon on a profile by manifest URL. The current addon list is read and preserved; only the new addon is appended. Supports dry_run and snapshots the previous state before the write; revert with nuvio_undo.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesAddon manifest URL
nameNo
dry_runNoReturn the diff without writing anything (no snapshot, no audit entry).
enabledNo
profile_idNo
sort_orderNo

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

A4.2/5.0
Behavior5/5

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

Beyond the annotations, the description discloses important behavior: the current list is preserved, dry_run is supported, the previous state is snapshotted, and the operation can be reverted with nuvio_undo. This gives an agent a concrete mental model of side effects and safety, which annotations alone do not provide.

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 tight sentences with no filler. The core purpose is front-loaded, and the behavioral details about append, dry_run, snapshot, and revert are packed efficiently without redundancy.

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 is adequate for a basic installation call, covering the required URL and key safety behavior. However, with six parameters, no output schema, and minimal schema descriptions for half the parameters, it leaves gaps around optional parameter semantics and success/return behavior that an agent would need for richer calls.

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 33%, so the description needed to compensate for undocumented parameters like name, enabled, profile_id, and sort_order. It does not: it only reiterates the URL-based install and dry_run support, both of which the schema already describes.

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 ('Install'), resource ('addon'), and mechanism ('by manifest URL'), and clarifies the operation appends to the existing addon list rather than replacing it. This clearly distinguishes it from sibling tools like nuvio_update_addon, nuvio_reorder_addons, and nuvio_remove_addon.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context: use this to add a new addon to a profile while preserving the current list. It does not explicitly name alternatives or state 'use nuvio_update_addon to modify existing addons,' but the append-only wording implies the boundary well enough.

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