Skip to main content
Glama
wiktorekdev

nuvio-mcp

by wiktorekdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Update an addon

nuvio_update_addon

Update an addon's name, enabled status, or sort order by URL or table ID. Preview changes with dry-run and revert anytime via undo.

Instructions

Change an addon name, enabled flag or sort order. Identify it by url or table id. Supports dry_run and snapshots the previous state before the write; revert with nuvio_undo.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
urlNo
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. Changed3 schema fields changedv1.1.1
    • 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

A4.1/5.0
Behavior5/5

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

Annotations only indicate the operation is not read-only and is not destructive. The description adds substantial behavioral context: it supports dry_run, snapshots the prior state before writing, and allows revert through nuvio_undo. This goes well beyond the structured annotation data and gives an agent a clear picture of side effects and safety.

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 two focused sentences with no filler. The first sentence fronts the core action and mutable fields, and the second adds identification and safety behavior. Every clause earns its place.

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 7-parameter write operation with no output schemaley, the description covers the main purpose, identifier choice, and safety mechanisms. It is not fully self-contained because profile_id has no documented purpose, no constraints on required identifiers are stated, and behavior for unspecified fields is not clarified.

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

Parameters3/5

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

Schema coverage is only 14%, so the description must compensate. It does connect name, enabled, and sort_order to the changeable fields and explains id/url as identification, which is useful. However, profile_id is left unexplained, and the phrase 'table id' is not precisely tied to the UUID-formatted id parameter, leaving some parameter semantics incomplete.

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?

Description uses a specific verb ('Change') on a specific resource ('an addon') and enumerates the mutable fields: name, enabled flag, and sort order. It distinguishes itself from sibling tools like nuvio_add_addon, nuvio_remove_addon, and nuvio_toggle_addon by clearly scoping what this update operation changes.

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 clarifies that the tool is for changing an existing addon and that identification is via url or table id, which is helpful. However, it does not explicitly contrast with nuvio_toggle_addon for enabled-only changes or nuvio_reorder_addons for sorting, nor does it state when dry_run should be preferred. Usage context 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